On Thu, 23 Sept 2021 at 15:42, Neil C Smith <[email protected]> wrote: > I've long felt that our use of JIRA and poor integration with the PR > process, etc. is more of a hindrance than a help, particularly during > releases.
Thanks everyone who has input here. Now 12.6 is out (just about) and branching for 13 is knocking on the door in mid-January, it would be good to wrap this discussion up into a plan that we can put in place by then. I think we have four options - 1. Move to GitHub issues, porting Airflow's model, configuration and automation, adapting where needed - https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=191332632 2. Stick with JIRA, but seek to address the sync issues between the two systems, including PRs, milestones, assignees, etc. As well as issue templates, removing access to fields like priorities, etc. from users? Add automation? Potentially make sure all PRs have a valid ticket? 3. Stick with JIRA as configured now. 4. Ignore JIRA issues entirely as part of the release process. I've made no secret I'm in favour of #1. And I'm happy to put some time into making that happen. Maybe others too? If #2, then some one/group needs to make that happen, and outline how, liaise with infra@ if needed, etc. Who's up for it? Is it actually doable? Happy to help here too, but it's going to be a lot more limited. Neither #3 or #4 feel tenable to me, although we're getting closer to #4 each release. If you're in favour of #3, thanks for offering to take on the next release though! ;-) Is there a #5? 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
