Yes, agreed -- clearly we need to be very disciplined with this release structure. But I think we did it the right way, i.e., we should have a very clear schedule, as we do know, but we should be flexible with it, as we have been -- and so long as we release by the end of the month, which seems very doable right now, we've proved it is workable.
Gj On Tue, Jul 16, 2019 at 11:58 AM Neil C Smith <neilcsm...@apache.org> wrote: > On Tue, 16 Jul 2019 at 10:48, Geertjan Wielenga <geert...@apache.org> > wrote: > > I think we should not add any new code to a vc, that's where things went > > wrong with vc1. It would be a cool thing to strive for: no new code in a > > voting candidate. > > I'm planning on documenting a few thoughts as we all review the new > release process, and that's already a top one from my point of view. > There was very little different in vc1, but it fixed a bug enabling > Payara Micro which led to this problem. > > Also interesting to think that we'll be about a week behind, and we > let some things slip feature freeze by a week which are actually the > things that have ended up causing that delay. Personally, I think > that's been worth doing, but it does bring up the importance of trying > to commit things early in any merge window. We should be wary of big > things landing late on. > > 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 > > > >
