JDK 9 forests open

[Coleen Phillmore]

On 1/3/2014 10:13 AM, Chris Hegarty wrote:
> On 3 Jan 2014, at 14:26, Coleen Phillmore <coleen.phillimore at oracle.com> wrote:
>
>> There are a lot of hotspot changes from jdk8 not in the jdk9 repositories as well.   Is someone merging them all in?
> The relevant quote from Mark’s mail [1].
>
>   "The JDK 9 development forests will be initialized from a specific
>    build of JDK 8.  After that build, merges between the two code lines
>    will not be permitted.  A developer who pushes a change into JDK 8
>    must also apply that change independently to JDK 9, if that change
>    is applicable to JDK 9.”
>
> We are following this process in the core area, and it is working well.

I think it's the case all of these changes to hotspot should be in jdk9, 
so we should bulk merge them rather than do them independently.  There 
are a lot and some depend on prior changes and our chance of missing one 
are too high.

I was wondering if someone was already doing this.

Coleen

>
> -Chris.
>
> [1] http://mail.openjdk.java.net/pipermail/jdk8-dev/2013-December/003766.html
>
>
>> thanks,
>> Coleen
>>
>> On 12/18/2013 2:41 PM, Joe Darcy wrote:
>>> On 12/18/2013 08:36 AM, Alan Bateman wrote:
>>>> On 13/12/2013 22:27, mark.reinhold at oracle.com wrote:
>>>>> The JDK 9 forests are open, per my previous message [1], except that
>>>>> "hotspot" is replaced by "hs" in the names of the HotSpot forests.
>>>>>
>>>> Just to double check one thing (and this ties into the thread on jdk8-dev on Managing parallel change).
>>>>
>>>> The jdk9 forests seem to be created from jdk8-b120. If I read the mails correctly then this means that anything pushed to a jdk8 integration forest that didn't make b120 needs to be pushed to one of the jdk9 integration forests, right? I just want to check because I see several changes in jdk8/tl that are not in jdk9/dev (not yet anyway).
>>>>
>>> Correct.
>>>
>>> -Joe
>>>