-
-
Notifications
You must be signed in to change notification settings - Fork 257
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Upstream openjdk/jdk(head) now branching releases rather than forking #3841
Upstream openjdk/jdk(head) now branching releases rather than forking #3841
Comments
Seems reasonable - am I right in saying this is purely during the stabilization process and the |
@sxa I think that is still being debated, I think there's suggestions that a branching in a new openjdk/jdk-updates might happen, if the jdk(head) experience goes well.... |
Yes. There will be a separate discussion for update releases (covering the |
The EA build status messages on slack will need updating too. It currently claims newest build tag for JDK 23 is |
Re-opening as this is not closed until #3852 is also merged. |
openjdk/jdk(head) will now be doing release branching, no longer forking repositories. See: https://mail.openjdk.org/pipermail/jdk-dev/2024-March/008834.html
This obviously means our jdk(head) mirror and jdk-23+ build-scripts will need updating
We currently have:
With the branching of the upstream “jdk23” branch, we now have no view of jdk-23, as our “release” branch is now jdk-24+1_adopt, and “dev” is jdk-24(HEAD)
My immediate thought is:
Thoughts?
The text was updated successfully, but these errors were encountered: