On Sat, 25 Sept 2021 at 08:12, Jaroslav Tulach <[email protected]> wrote: > An Apache project like NetBeans doesn't need more incoming bugs, it needs more > incoming fixes!
+1. But we do have something of a bug management issue, particularly during releases. > Enough of sad bitter like-to-be truthful irony. Me and my OracleLabs > colleagues need to track issues and fixes on many fronts. In the internal > JIRA, > in the NetBeans JIRA and connect it all with pull requests. It would be a little less complicated. If we took the approach that Airflow have, that scenario would not have an issue at all on the NetBeans side - pull requests are the primary change record. That actually seems more in line with the more useful old bugzilla links? There's another good follow up from Jarek on how they transitioned and how they're managing things. I've read a number of good and detailed posts from Jarek on a variety of infrastructure issues recently. And looking at how other ASF projects address similar concerns is always good, even if we end up deciding it's not for us. https://lists.apache.org/thread.html/ra580969453a8491d71b9926d1147de1521dd76f74847a42779186160%40%3Cusers.infra.apache.org%3E Shame this is on a list with private archive. I hope selective quoting is not much of an issue, though - this paragraph seems quite apt amongst others - """ A lot of issues we had in jira were already out-dated or of poor quality, so that automatically cleaned up the state of our issues. I personally think that if it is not obvious that an issue is really important and if the author of the issue is not interested in adding extra information if asked or if they are not following up with them - they are better if they are "forgotten". They add no value to the project, they only add "noise". This is why I love GitHub discussions so much. We can convert the issue to GitHub Discussion if we look at it and it is likely the issue is caused by user error, deployment issue etc. This does not "close" the issue (which is quite mean) - but it moves the "responsibility" for the discussion to continue on the author - it's a very clear sign that the discussion might be left in the state of "discussing it" and there is no intention or expectation that it will be fixed. And we can always create an issue from the discussion if we get to the conclusion this is a real issue. This already happened in the past. """ > Btw. thinking about switching to GitHub Issues shows that Microsoft, after > taking over the GitHub, is doing really good job and is re-gaining the trust > of open source communities. I know, be Oracle next! :-) Best wishes, Neil --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
