Hi,
Thanks to all, we've released VSNetBeans 24.9.9 in January using partially the 
proposed process. It went well in my opinion, although not done really in 
parallel with active release250 & delivery branches.

I would like to continue the discussion and have some questions. Will do it as 
timeline summary

1. Jan 16th - I’ve created VSNetBeans_249 branch. I did it after Eric Barboni 
on Slack confirmed it is OK "I think it's ok. I've just removed delivery 
branch” 

2. After building 2 vote candidates VSNetBeans released on 24.1. It took 9 days.
3. NetBeans 25 release_250 was created by Eric on 24.1. as announced on 17.1.

—
Question: Is it the problem if `delivery` branch coexist with other release 
branch which does not pick all commits from delivery? 
On 16.1. delivery branch was there since release 24.0 so it was going to be 
rebased anyway.  

Commits done to vsnetBeans_249 will not affect the ‘old' delivery. And if new 
delivery used for release_250 would be active then commits will go to delivery 
1st and then to vsnetBeans_249 if this fix is the must for both. I don’t see 
there problems with git itself. Is this the process issue or GitHub issue??

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. Therefore 
delivery and vsnetBeans_xyz branch will coexist in some time slots during the 
year.

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)
—

4. Next VSNetBeans release will be 25.0 together with NetBeans 25.0 in Feb.

Proposed VSNetBeans schedule:
5. VSNetBeans 25.x.x branch around March 8th from master to match JDK release 
on March 18th. (Version tbd)
6. VSNetBeans 25.x.y branch around April 4th from master to match JDK release 
on April 15th. (If this needs to happen at all)

7. NetBeans 26 release_260 branch created on or slightly after 15.4. -> release 
both NetBeans IDE and VSNetBeans in May
8. … and so on...

What do you think?
Martin
 


> On 9. 1. 2025, at 19:32, Martin Balín <mart...@windowslive.com> wrote:
> 
> Hi,
> 
>> On 9. 1. 2025, at 11:11, Neil C Smith <neilcsm...@apache.org> wrote:
>> 
>> 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.
> This sounds good.
>> 
>> 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.
> So, applying above to upcoming NB 25 release schedule means. Release branch 
> for NetBeans 25 on Jan 15th, or so and same commit used also for VSNetBeans 
> 24.9 release.
> VSNetBeans 24.9 releases Jan 21st or soon after with upcoming JDK release 
> dates.
> NetBeans 25 releases around Feb 15th.
> Martin
>> 
>> 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 
> <mailto:dev-unsubscr...@netbeans.apache.org>
> For additional commands, e-mail: dev-h...@netbeans.apache.org 
> <mailto:dev-h...@netbeans.apache.org>
> 
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Reply via email to