[11u] Proposal: Switch jdk11u development to Git/Skara with 11.0.13 cycle
christoph.langer at sap.com
Wed Feb 10 16:39:24 UTC 2021
after most of the OpenJDK projects, including OpenJDK updates 13u and 16u, have already moved to git, we'd like to propose the transitioning of 11u to git as well. The topic has been brought up in a few discussions already, e.g. .
Our proposal would be to move the JDK 11 updates project to Github/Skara with the 11.0.13 development cycle. The git switch of jdk11u-dev should happen on June 2, 2021, which is when 11.0.13 development starts. With the first promotion of 11.0.13 to the jdk11u stabilization repository on August 3, 2021, we would then also switch the jdk11u repository to git.
This means that On June 2, 2021, the jdk11u-dev mercurial repository  would be made read-only and changes for 11.0.13 ought to be pushed to the jdk11u-dev github repo . On August 3, 2021, the jdk11u mercurial repo  would be set read-only and the equivalent git repo  will be opened for pushes. After the moves, the mercurial repositories will contain 11.0.12 and be updated no further.
This is why we think the project should move to git:
* Git/Github is used by the OpenJDK project in head and the higher update releases. JDK11u will certainly benefit if it uses the same processes
* The tooling and infrastructure (Skara) is the maintained set of tooling
* The Git/Skara processes have the potential to simplify the backporting processes and could improve the productivity in the JDK 11 updates project
* Git is probably the most prevalent SCM for downstream consumers which means that the downstream processes to consume the git repositories should largely be available by now or can be made available until the time of the switch without extraordinary cost
At the time of the 11.0.13 cycle, the backport tooling should have reached a convenient state of maturity, suitable for the 11u project.
Looking forward to your thoughts and arguments...
Christoph and Goetz
More information about the jdk-updates-dev