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

[David Holmes]

Hi Joe,

On 1/09/2017 11:12 AM, joe darcy wrote:
> An update on the repo consolidation.
> 
> 
> On 8/25/2017 1:52 PM, joe darcy wrote:
> 
> [snip]
> 
>>
>> 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.
>>
> 
> As has been discussed on hotspot-dev [1], the JDK 10 integration forests 
> are working on getting their outstanding fixes integrated into JDK 10 
> master ahead of the repo consolidation. The client forest is following a 
> similar pattern. The hotspot integration is expected before September 4 
> and the client integration is targeted before September 9. Once the last 
> expected fixes are in the integration forests, the forests will be 
> closed to pushes from people other than those working on the integration 
> to master. (The integrators may need to address problems in the 
> integration, etc.)
> 
> Likewise, early in the week of Sept. 4, the JDK 10 master forest will be 
> configured to only allow pushes from integrators and people working on 
> the consolidation. The master line of development will remain in that 
> state until the consolidation is complete.
> 
> The final pre-consolidated version will be tagged as build N. The 
> functionally equivalent consolidated sources will be tagged as build (N+1).
> 
> The current plan for the top-level JDK 10 forests is:
> 
> * jdk10/jdk10 -- pre-consolidated version archived and ready-only to 
> allow URL links from JBS to continue to function
> * jdk10/master -- new consolidated master repository hosted the sources 
> previously spread out in jdk, langtools, hotspot, etc.
> * jdk10/client -- old "client" forest deleted, new "client" repo created 
> as a child of the consolidated master
> * jdk10/hotspot -- old "hotspot" forest deleted, new "hotspot" repo 
> created as a child of the consolidated master

The existing forest is jdk10/hs not jdk10/hotspot, but renaming the new 
repo as "hotspot" might be a good idea.

> An implication of the above is that existing children of the 
> pre-consolidated forest will no longer be directly usable for doing 
> pushes. New clones of the appropriate consolidated repo will need to be 
> used instead once the repos are opened for development.

Any tools for making this migration easier? I personally have 6 clones 
I'd need to migrate.

How do the project repos move across to the new consolidated form? Will 
we lose all the changeset history?

Cheers,
David

> We are aiming to have all the necessary infrastructure changes in place 
> to reopen development by the week of September 18. I'll be given updates 
> on progress in the interim.
> 
> Comments?
> 
> Cheers,
> 
> -Joe
> 
> [1] 
> http://mail.openjdk.java.net/pipermail/hotspot-dev/2017-August/028134.html