Update on JDK 10 repo consolidation; consolidation planned for September 2017

Joseph D. Darcy joe.darcy at oracle.com
Tue Jun 27 23:23:37 UTC 2017


With JEP 296: "Consolidate the JDK Forest into a Single Repository," now 
targeted to JDK 10, I wanted to give an update on the planned timing of 
the consolidation.

We are looking to perform the consolidation in September of this year. 
Doing the consolidation at that time will allow essentially all of the 
expected JDK 9 [2] fixes to get into 10 through forward porting from Hg 
syncs [3]. Key personnel for the project will also be available at this 

A rough outline of the subtasks of the consolidation:

All outstanding changes from JDK 9 and from child integration forests 
(hs and client), will need to get integrated into JDK 10 master. The 
particular JDK 9 build to be used as the last source of changes for JDK 
10 will be communicated when that is known. After that point, any fixes 
to go into both JDK 9 and JDK 10 will need to be pushed separately.

An integration of the state of JDK 10 after collecting the fixes above 
will be done and tagged. The child forests will be marked read-only.

The JDK 10 sandbox will also be marked read-only and users of the forest 
will be advised to migrate their patches out. Likewise for project 
forests that are children of JDK 10.

The JDK 10 master forest will be marked as read-only and the 
consolidation conversion process run on a copy. A new master forest with 
a new name will be created and published. Another JDK 10 integration 
will be performed on the new master post-consolidation. While the 
contents of the sources at a file-level are expected to be the same 
before and after the consolidation, the build system will be different 
and the file locations altered.

The old integration forests and sandbox will be deleted and new 
consolidated versions created.

Boundary systems will be adjusted to work with the consolidated layout.

After that point, the new consolidated repository will be open again for 
business. During the consolidation process, I'd expect a nontrivial 
period of time where JDK 10 master was unavailable to accept changes, 
say two weeks. The integration forests will also be unavailable for a 
somewhat longer period of time starting from their last integration to 
master until the new master is created and open.

More details on the plan will be developed as the consolidation gets closer.




[1] http://mail.openjdk.java.net/pipermail/jdk10-dev/2017-June/000296.html

[2] http://openjdk.java.net/projects/jdk9/


More information about the jdk10-dev mailing list