JEPs proposed to target JDK *16*: 357 (Migrate from Mercurial to Git) & 369 (Migrate to GitHub)
joe.darcy at oracle.com
Tue May 19 18:44:28 UTC 2020
FYI, assuming the JEPs get targeted, a bit more detail on the Skara
team's current SCM transition plans for JDK 16.
We are looking at transitioning the jdk/jdk repo hosted on github.com to
become the read/write master for JDK 16 sources in early September 2020.
This would be a few weeks before the GA date of JDK 15 and after a
separate JDK 15 repo is forked off in mid-June per the JDK 15 schedule
The early access JDK 16 builds published on http://jdk.java.net/ may
transition to being Git-based rather than Mercurial-based some time
ahead of the repo transition. Which SCM is used as a basis for a JDK
build can be inferred from the contents of the "release" file in the
root of the build. Among other information, the release file records the
SCM and the SCM hashes of the sources used for the build.
On 5/18/2020 4:18 PM, mark.reinhold at oracle.com wrote:
> The following JEPs are proposed to target JDK *16*:
> 357: Migrate from Mercurial to Git
> 369: Migrate to GitHub
> Feedback on these proposal from JDK Project Committers and Reviewers 
> are more than welcome, as are reasoned objections. If no such objections
> are raised by 23:59 UTC on Monday, 25 May, or if they’re raised and
> then satisfactorily answered, then per the JEP 2.0 process proposal 
> I’ll target these JEPs to JDK 16.
> - Mark
>  https://openjdk.java.net/census#jdk
>  https://cr.openjdk.java.net/~mr/jep/jep-2.0-02.html
More information about the jdk-dev