Hi, I think we are heavily overcomplicating things. We had a phase where we wanted to do timebased releases. Given this whole discussion, I think it would be the right moment to revisit that idea.
Lets consider NBCode would do the same as NetBeans IDE, then we would at times have to "delivery" branches, which get fixes independend from each other. At the end the two flavors would have a different bugfix level, as currently merges are delivery->master only, and thus fixes never reach a secondary release branch. This also raises the question why NetBeans IDE needs a multi RC phase, while NBCode does not. While I'm not interested in NBCode or the whole "OCI" thing, I don't see value in splitting repos or issues. Of course there are issues specific to NBCode and NetBeans IDE, but the core parts are shared and so apart from two places to look for I see little value. Greetings Matthias Am Freitag, dem 31.01.2025 um 16:31 +0000 schrieb Neil C Smith: > On Fri, 31 Jan 2025 at 16:05, Martin Balin <mba...@apache.org> wrote: > > I’m asking this as using same date for NetBeans IDE and VSNetBeans > > branching (if these are close enough) was proposed earlier in this thread. > ... > > JDK releases are usually closer to 15th of the month therefore it will be > > better if VSNetBeans can branch ~ 10 days prior JDK days, from master, > > using vsnetBeans_xyz branch. (See proposed schedule below) > > And that proposal is still, IMO, how this should be done. Why not a > change to the branch dates if you need it to be earlier, as was > suggested? Having different branch dates too close together is going > to be a problem for stability. > > > Therefore delivery and vsnetBeans_xyz branch will coexist in some time > > slots during the year. > > That was expected. As long as everything going into master goes via > delivery, that's not a problem. If you're cherry picking commits to > vsnetbeans(?), you could cherry pick from whichever branch you want. > > > (Version tbd) > > It would be good to use separate version numbers, and a separate > branching repo with your own issue queue, milestones, etc. This is > already a point of confusion. > > Personally I'd also like to see a hard limit on the number of > VSNetBeans releases between IDE releases in case of release delays in > future. > > 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
