On Thu, 9 Jan 2025 at 09:20, Svata Dedic <svatopluk.de...@gmail.com> wrote: > On 05. 12. 24 16:20, Neil C Smith wrote: > > That looks like it could work with a fixed monthly branch date, even > > if not all get used. The important thing is to have a shared branch > > date with the IDE in those months that need both. Or to keep the > > branch dates far enough apart, but I can't see that working with that > > schedule. > > Apologies, I got lost in the wording. Could you please give an example > how do you think the branch + date coordination should work and what are > the important coordination points/concepts from your point of view ?
With the stabilization that goes in towards freeze and branch, trying to do that for different dates within a week or two of each other will be a nightmare. The notice emails that usually go out in the weeks preceding freeze emphasise being "release aware". That's difficult to achieve if working to different dates. So, I'm suggesting picking a date of each month on which branch can happen, even if the IDE, or even both releases, don't use it. Currently that would be around the 15th (rarely exactly 15th), but that can be changed. We have a policy of keeping master in a releasable state already. That would be particularly important 7th-15th of every month. In the months that both the IDE and VSNetBeans projects branch, we branch from the same commit on master, coordinated between release managers. VSNetBeans release does not have to wait for the IDE to release as now. The branch point is more of a concern than the release date. 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
