Repo consolidation update: jdk10/master, jdk10/client, and jdk10/hotspot open for pushes

[Daniel D. Daugherty]

No. We still haven't been able to execute HotSpot specific testing
on the repo. Calvin has been trying to push a fix for one of the
problems, but JPRT is _not happy_ with the new JDK10/hs repo...

Stay tuned. People are working on it.

Dan


On 9/22/17 8:38 AM, coleen.phillimore at oracle.com wrote:
> Can we check stuff in to jdk10/hs yet?
> thanks,
> Coleen
>
> On 9/20/17 8:17 PM, Mikael Vidstedt wrote:
>> All,
>>
>> TL;DR: jdk10/hs remains closed for now.
>>
>> As Joe mentions the consolidated jdk10/hs repo has been created, but 
>> please hold off on pushing anything for now. We’d like to have some 
>> time to do a full test run and verify that we start off with the new 
>> repo in a known good state. Hopefully we’ll have the necessary test 
>> result data within the next day or two and if everything looks good 
>> the repos will be opened.
>>
>> Thanks,
>> Mikael
>>
>>> On Sep 20, 2017, at 3:12 PM, joe darcy <joe.darcy at oracle.com> wrote:
>>>
>>> Hello,
>>>
>>> The JDK 10 master line of development at
>>>
>>>     http://hg.openjdk.java.net/jdk10/master/
>>>
>>> and the two integration lines of development at
>>>
>>>     http://hg.openjdk.java.net/jdk10/client/
>>>     http://hg.openjdk.java.net/jdk10/hs/
>>>
>>> are now open for pushes. All three are consolidated and are 
>>> currently equivalent to JDK 10 b24.
>>>
>>> Consolidated versions of other JDK 10-derived lines of development, 
>>> such as for Project Amber, Project Valhalla, and the sandbox, will 
>>> be created in the coming days.
>>>
>>> If you have clones of any of the old non-consolidated JDK 10 forests 
>>> with outstanding work to bring over, you can:
>>>
>>> * Synchronize the old forest with jdk10/jdk10. The jdk10/jdk10 
>>> forest is an archive of the non-consolidated master forest at build 
>>> 23. Before being closed to pushes, both the jdk10/client and 
>>> jdk10/hs forests were synchronized with jdk10/jdk10.
>>>
>>> * Extract the patch of the in-progress work.
>>>
>>> * Run the patch through the patch conversion script, 
>>> bin/unshuffle_patch.sh in the consolidated repository.
>>>
>>> * Apply the converted patch to a clone of a consolidated repo and 
>>> resolved any conflicts, etc.
>>>
>>> Thank you to the many people who worked on the consolidation project!
>>>
>>> Cheers,
>>>
>>> -Joe
>>>
>