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

[Kevin Rushforth]

On 3/22/2024 9:12 AM, Magnus Ihse Bursie wrote:
> On 2024-03-20 17:20, Iris Clark wrote:
>
>> I propose that the JDK feature releases (e.g., JDK 23, JDK 24) use 
>> branches
>> rather than repositories for stabilization.  The "master" branch will 
>> continue
>> to be the always-open default branch, used for main-line 
>> development.  Instead
>> of a stabilization repository "jdk$N" (where $N is the version number 
>> of the
>> next release, e.g. "jdk23" or "jdk24"), we will use a stabilization 
>> branch
>> with the same name, "jdk$N".  Changes will be backported from the master
>> branch via pull requests targeting the release-specific stabilization 
>> branch.
>> The stabilization branch will be locked when the release is delivered.
>>
>> I suggest that we adopt this proposal for JDK 23 RDP 1, June 2024.
>>
>> Concerns?
>
> Since I have not seen much feedback, I'd like to emphasize my support 
> for this proposed change. The only concern I have is "What took us so 
> long?" (and yes, I understand why it took so long). :-) But maybe the 
> lack of feedback is just an indication that everyone agrees with this.
>
> As with all changes, I anticipate some minor hiccups. Ideally, they 
> will all be resolved prior to the switch. However, that small risk 
> should not stop us from starting to use this, much saner, model.

I also fully support this proposed change. We have been successfully 
using a branching model for stabilizing JavaFX feature releases in the 
jfx repo for about 4 years.

-- Kevin