[11u] Proposal: Switch jdk11u development to Git/Skara with 11.0.13 cycle

[gouessej at orange.fr]

Hello

 

Sorry, maybe it's a bit late or silly but will it still be possible to get the source code of OpenJDK >= 11.0.13 and to contribute without using Github? Git != Github. I have nothing against Git, I understand the advantages of the transition but Github is owned by Microsoft, I hope that the mercurial repositories will be kept on the long term and I hope that a Github account won't become mandatory to contribute. I'm worried about the important concentration of open source projects in a single platform controlled by a single company (and as charity begins at home, I have no Github account).

 

Best regards.

 

> Message du 10/02/21 17:40
> De : "Langer, Christoph" 
> A : "jdk-updates-dev at openjdk.java.net" 
> Copie à : "Lindenmaier, Goetz" , "Andrew Haley" , "Severin Gehwolf" 
> Objet : [11u] Proposal: Switch jdk11u development to Git/Skara with 11.0.13 cycle
> 
> Hi,
> 
> 
> 
> 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. [0].
> 
> 
> 
> 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 [1] would be made read-only and changes for 11.0.13 ought to be pushed to the jdk11u-dev github repo [2]. On August 3, 2021, the jdk11u mercurial repo [3] would be set read-only and the equivalent git repo [4] 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...
> 
> 
> 
> Best regards,
> 
> Christoph and Goetz
> 
> 
> 
> [0] https://mail.openjdk.java.net/pipermail/jdk-updates-dev/2020-December/004450.html
> 
> [1] http://hg.openjdk.java.net/jdk-updates/jdk11u-dev
> 
> [2] https://github.com/openjdk/jdk11u-dev
> 
> [3] http://hg.openjdk.java.net/jdk-updates/jdk11u
> 
> [4] https://github.com/openjdk/jdk11u
> 
>