Hi Will try to fix delivery now. I hope nobody needs to PR to that branch.
-----Message d'origine----- De : Neil C Smith <> Envoyé : dimanche 22 mai 2022 10:59 À : dev <dev@netbeans.apache.org> Objet : Re: [RELEASES] 14 remaining issues Hi, On Sun, 22 May 2022, 04:27 Jaroslav Tulach, <jaroslav.tul...@gmail.com> wrote: > ...but when I studied the `delivery` rules the last time, the #1 rule was: > No > mere developer can press the merge button - a release coordinator has to. > If > the rule still applies, then it is the release team who ultimately > decides what to merge into `delivery` (and I am fine with that). > We've never decided what gets merged. The release team handle merges to delivery for various scheduling, technical, requirements reasons. We don't decide what gets merged (any more than any other committer does anyway). The PR review process for delivery should cover justifications for why a PR needs to go into delivery / the release. All PRs that pass that review process will be merged to delivery. Every change to delivery forces another release candidate cycle. Usually that adds a week, although we can shorten that a bit. If you open a PR to delivery, particularly at this point at the cycle, it is effectively also a request to delay the release on it. Thanks for the additional info on background for this PR. Delivery will need fixing before it can be merged, which might require it to be updated. 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
