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

[Mark Reinhold]

2024/3/20 12:20:34 -0400, iris.clark at oracle.com:
> ...
> 
> 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?

Iris -- thanks for making this proposal [1].

The initial discussion was generally positive.  Further feedback from
JDK Project Committers and Reviewers [2] is welcome, as are reasoned
objections.  If no such objections are raised by 23:59 UTC on Tuesday,
21 May, or if they’re raised and then satisfactorily answered, then
we’ll adopt this practice for JDK 23, for which RDP 1 is coming up
soon on Thursday, 6 June.

- Mark


[1] https://mail.openjdk.org/pipermail/jdk-dev/2024-March/008834.html
[2] https://openjdk.org/census#jdk