Update on JDK 10 repo consolidation; third generation prototype coming soon, September 2017 still the target

[joe darcy]

Hello,

A follow-up to the most recent update [1] on the JDK 10 repo 
consolidation efforts, September 2017 is almost upon us and that month 
remains the target to implement the repo consolidation.

First, a third generation prototype having tags from both JDK 9 and JDK 
10 will be published in the near future.

Afterward, the previously outlined plan will be executed; quoting from [1]

> 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.

Since there are no further fixes currently planned for JDK 9, any 
subsequent fixes made to 9 will likely need to be separately pushed to 
JDK 9 and JDK 10.

We're aiming to have the final pre-consolidation integrations of the hs 
and client forests into JDK 10 master the week of August 28 or shortly 
thereafter. Any work urgently needed to JDK 10 in areas that push 
directly to master should also be pushed the week of August 28.

On or about the week of September 4, JDK 10 master will be marked as 
read-only and after it is marked read-only, no changes will be accepted 
into the conceptual JDK 10 master line of development until after the 
consolidation is complete and the necessary infrastructure to support 
the consolidation updated.

Cheers,

-Joe

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