JDK 10 forests open for bug fixes and small enhancements

[David Holmes]

On 27/01/2017 2:12 AM, Jesper Wilhelmsson wrote:
> I'm not the decision maker here, but this is what was said in a meeting:
>
> The jdk10/jdk10 forest will sync with jdk9/dev. New changes in jdk9/dev
> is pulled into 10 this way. The process is planned to be made automatic
> using Mach 5 but initially Lana and I will be doing the integrations.
>
> jdk10/hs is a child of jdk10/dev. For changes to go from jdk9/hs to
> jdk10/hs they will have to go through 9/dev and 10/dev. This is assumed
> to take a while. Right now we only integrate 9/hs to 9/dev once a week,
> and at most we can crank that up to twice a week due to the rigorous
> testing requirements. Once we get Mach 5 support for HotSpot testing
> (running all the required VM tests) we can start integrating more often.

Thanks Jesper. So it is going to be a while before we have a jdk10/hs 
that we can reliably push to via JPRT. We will also have to watch for 
issues introduced in jdk9/dev (which we would fix in jdk9/hs) getting 
taken into jdk10/dev and then jdk10/hs, as the fix will take a long time 
to reach jdk10/hs!

David

> HTH,
> /Jesper
>
> Den 26/1/17 kl. 14:43, skrev Philip Race:
>> So there is an expectation that 10-hs is seeded from 9-hs and so forth ?
>> I guess not just for seeding, but on-going the sync will be from
>> jdk9/jdk9
>> no matter what the destination forest.
>>
>> -phil..
>>
>>
>>
>> On 1/26/17, 4:31 AM, Alan Bateman wrote:
>>>>
>>> The jdk10 forests seem to be seeded with jdk-9+153, I suspect David
>>> is looking for changes are that backed up in jdk9/hs and haven't made
>>> it into a JDK 9 promoted build yet.
>