It will keep jenkins busy and trigger a build per commit and do all release stack. Only if a release date for release160 is set in the json, jenkins will do apidoc only.
Using delivery may be more Jenkins friendly but I don't think it's a human :p. Eric -----Message d'origine----- De : Neil C Smith <neilcsm...@apache.org> Envoyé : jeudi 1 décembre 2022 14:52 À : dev@netbeans.apache.org Objet : Re: [DISCUSSION] Gradle Patch Release for NetBeans 16 On Mon, 28 Nov 2022 at 15:55, Neil C Smith <neilcsm...@apache.org> wrote: > > On Mon, 28 Nov 2022 at 15:43, László Kishalmi <laszlo.kisha...@gmail.com> > wrote: > > release161 branch has been removed, PR-s have been re-targeted to > > release160. > > Great, thanks! I'm just waiting on votes for rest of additional > binaries to start and I'll close the main vote. Want to make sure > everything is OK before we merge anything else into the branch. OK, everything done that needs to be done, so release160 can be considered open again for merging. However, I wonder whether we should have a transient branch like delivery (now deleted) for merging into? Merges into release*** branches trigger a lot of things. Eric? 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 --------------------------------------------------------------------- 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
