On Thu, 11 Nov 2021 at 15:44, Michael Bien <[email protected]> wrote: > I do like the github issue tracker since it appears to be simpler while > still doing its job. To keep an issue tracker useful, it does need > maintenance though. E.g many projects automatically close issues if they > are inactive for a certain amount of time. Having 32k open issues on > jira like NB has, is no longer observable. > > Many "critical" issues i commented on asking if its still a problem were > in fact already fixed. This has to be automated, nobody should have to > do that manually. If the original poster cares about the issue and its > closed by mistake, believe me, it will be reopened. > > > i am for github issues, but someone would actually have to write the > templates, and then also try to automate things, otherwise it will be > jira 2.0 in a year or two.
Absolutely! I'm basically saying let's follow what Airflow are doing, and tweak where needed, rather than do this from scratch. They're an ASF project that seemed to have the problems we have, and seem to have addressed it in a way that we could use as a model - forms, automation, etc. included. I'm for doing this for the same reason I was for ditching LTS - it's a promise to our users we're not keeping. It feels worse than useless right now - 32k open issues is just a black hole for users to vent their frustrations into. We really need fewer, better quality issue reports. So, why not see if we can learn from other ASF projects who have been through this? It can't be worse! :-) 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
