Proposal: Branch github.com/openjdk/jdk for stabilization (instead of fork)

[Kevin Rushforth]

On 3/21/2024 4:07 AM, Severin Gehwolf wrote:
> On Thu, 2024-03-21 at 11:42 +0100, Volker Simonis wrote:
>> This proposal sounds interesting and reasonable.It would be especially
>> beneficial if the JDK Updates Project (added to CC) would adopt this
>> new model.
> We can consider it for jdk-updates at a later point. I don't think it's
> good to conflate those two at this point. Lets get mainline JDK
> development switched, first. See how it pans out for mainline and
> corresponding downstream consumers.
>
> Once we have that experience, we could model it for jdk-updates further
> down the line.

I agree. This proposal deliberately does not address update releases. 
Any changes to update releases would necessarily need a separate 
proposal with its own discussion. Waiting to see how it works in 
practice for the JDK Project seems wise.

If and when the JDK Updates Project makes a proposal to switch to 
branches, the repository and branch structure -- specifically, whether 
to continue to have a per-release-family jdkNNu repo vs moving to a 
single jdk-updates repo -- would be a big part of that discussion. I 
have an opinion on that, based on experience with our internal update 
releases and with the GitHub workflow, but will leave it for that later 
discussion.

-- Kevin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/jdk-dev/attachments/20240321/722810fa/attachment.htm>