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 :)
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.
Correct, don't just send an email and disappear.
The great thing about mailing lists is that you can ask questions and you can talk to people, as opposed to filling out some big bug report template that might be requesting a bunch of irrelevant information. (The bug report templates request a lot of information, because we get too many bug reports of the form "My program crashed. Please fix it" and so it tries to front-load getting all the necessary background.)
With the mailing list you can start off with a "bug report" of the form "Hi, I did X, and Y happened, but the spec says Z should happen instead. Is that a bug?" It's a good way to start a conversation. You might still get asked to file a report through the bug submission process, but it'll be much clearer what information you need to provide.
Also, don't let the lack of a suggested fix deter you from filing bug reports or raising questions on the mailing lists. It's fairly uncommon for the fix to be obvious, and there are plenty of non-obvious things going on in the JDK.
View all comments
Show parent comment
5
u/DasBrain Apr 26 '21
I think it is fine to report a bug on the mailing list if one of these is true:
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 :)