Thanks, you've done a great job of explaining what you have to do. And yes, we know that the bug-reporting process leaves quite a lot to be desired. You could probably have saved some time by approaching the core-libs-dev list at the start, but that's the only thing that might have worked better. Nice one.
While I find the whole process a bit obtuse and like to argue vehemently against the use of mailing lists, I find that the people who participate on the mailing lists are quite helpful and almost always respond seriously to all kinds of questions and proposals, even if they have been asked or discussed many times before.
I think it is fine to report a bug on the mailing list if one of these is true:
You are already an active participant of that mailing list.
You intend to provide a patch, fixing the bug yourself.
Or, in other words: please don't report bugs on the mailing list and then disappear.
The bug that was fixed is an excellent example for a first bug to fix - a method that doesn't conform to it's specification.
Fixes for such bugs are often a one or two line change - but you also need to provide regression tests.
Once two of your patches have been accepted, you can apply for the author role of that project - it boils down to writing an email (template is provided), waiting, filling out a form, more waiting, and resetting your password with the "forgot password" option.
Then you have full write access to bugs.openjdk.java.net, which makes reporting future bugs much easier :)
37
u/AndrewHaley13 Apr 26 '21
Thanks, you've done a great job of explaining what you have to do. And yes, we know that the bug-reporting process leaves quite a lot to be desired. You could probably have saved some time by approaching the core-libs-dev list at the start, but that's the only thing that might have worked better. Nice one.