> On 12. 11. 2024, at 16:00, Michael Bien <mbie...@gmail.com> wrote:
>
> On 12.11.24 15:40, Neil C Smith wrote:
>> 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,
Not monthly. VSCode plugin will release around JDK releases
https://www.java.com/releases/ incl CPU.
Java support released with JDK releases.
As this is Java developer tool and VSCode extensions ecosystem is fast changing
this works. Given short period of time between releases stabilization cycle can
be short as well for module set included in VScode ext
Martin
>
> this detail would be a key requirement for this discussion. Without knowing
> how frequent the releases are intended to be, it is very difficult to make
> suggestions since it influences the setup.
>
> Cherry-picks work ok for update releases which contain bug fixes and
> occasionally a feature.
>
> If we are talking about something which is closer to rolling releases, it
> would have to branch from master most likely.
>
> (I do not strongly oppose branching from master as already mentioned, but
> lets not release the equivalent of JDK 24ea build 1. Master is to be expected
> to be more stable when NB stabilizes)
>
> -mbien
