On Tue, 12 Nov 2024 at 14:17, Michael Bien <mbie...@gmail.com> wrote: > I mentioned at the end of the mail that this _could_ also simply fork > from master at random times and also why I am not a big fan of this idea.
Well, I don't think the distinction needs to be between branching from the release and branching from master at random times. At present the IDE has a fairly specific branch point at ~15th of every third month. Say if the VSCode plugin wanted to release monthly, they could branch at ~15th of every month. Every third month, the IDE and plugin branch on the same date from the same point on master. I would be concerned if we had random branching, particularly within a week or two either side of the IDE release branching. That's a recipe for chaos, and should probably not be allowed in any solution we arrive at. Branching on the same date does not mean the VSCode plugin has to wait to release with the IDE. It can still stabilise and release quickly. Decoupling release dates is potentially simpler than totally decoupling branch points. If ~15th in that scenario doesn't work for the VSCode plugin then we could change the IDE branch date to be earlier or later in the month. 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
