On Sat, 4 Dec 2021 at 15:39, Eric Bresie <[email protected]> wrote: > I still think there needs to be a "#5 Establish, document, and use a > process to manage the issues" that should be addressed. > > The best integrated issue, CM, > and discussion tool in the world is only as good as the “process” to manage > it.
Obviously! Which is why my proposal in #1 has always been to start with Airflow's existing process as a model. Choice of tool has always been secondary IMO. The majority of what you ask is answered in that wiki page. If we can filter down to what isn't, what might need adapting, etc. that would be useful. I'm sure a lot (probably not all) of that process could be adapted to work in JIRA too. Just there's likely more work to define / make happen. Who? How? What? The key thing in my mind is that this is just getting harder to manage and less useful with each release, and I'd really like to see something better by the time we branch 13. >From a release management perspective this is not working! Incidentally .. On Sat, 4 Dec 2021 at 13:11, Geertjan Wielenga <[email protected]> wrote: > We should formally announce that we’re no longer accepting issues, just > discussions, in which the reporter owns what they report on, from the start > to the end (i.e., testing) of the process. That may be a bit too close to #4. :-) The emphasis in #1 should be to reduce the noise and raise the bar for reporting issues, such that issues become a useful tool for release management, rather than push everything into discussions. Otherwise it may be a little too close to the chaos we have in JIRA now. 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
