Hi Eric, Martin, Geertjan .. and everyone else, Just thought I'd kick off a thread as it's getting near branching time again. Seems to come around quicker every time! I also realised I don't think we had the usual postmortem thread on NB14 either. Any points, changes, etc. to address for 15?
Few from me would be - There were a couple of PRs in NB14 that to me didn't really meet the criteria for merging to delivery, one which potentially held the release up. It's not a release team job to decide what gets merged - that's for all reviewers. And primarily, in my mind, the PR author should be making the initial call. I'd like to suggest that all descriptions on PRs for delivery, at least when not linked to an issue, should include a short justification for inclusion. Thoughts? On PRs, Martin, can you handle reviewing and merging delivery PRs (or parts) that are VSCode related? Obviously need to schedule around syncing and RC builds. Whenever I merge to delivery, I try to test the fix, check for potential conflicts, think about highlighting in RC emails, etc. But for me that's with the IDE in mind rather than the VSCode plugin. As discussed elsewhere, I've added a GitHub label for Highlight, to try and start flagging PRs that are changes to highlight in release notes, announcements, etc. Possibly need to apply some retrospectively for 15. I should be OK for all of this release cycle - sorry I had to duck out for much of the last one. I'm happy to handle the initial branch and configuration around July 15th, unless anyone else wants to? Anyone else got commitments, holidays, etc. to consider this time around? Summer release always a fun one. Best wishes, Neil --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
