Managing parallel change in JDK 8 and JDK 9
Volker Simonis
volker.simonis at gmail.com
Tue Dec 3 09:46:47 PST 2013
Hi,
thanks for your replies. I was only afraid that we would have to go
trough a new round of reviews if we have to get new Bug-IDs for every
change.
But Iris just clarified that we will get a second, JDK 9 staging
repository once JDK 9 will be forked. So we will have to down- or
up-port our ppc-aix changes to both staging repositories afterwards.
But for this extra work we will have the benefit that we will be able
to immediately bulk-integrate ppc-aix-stage into the corresponding
jdk8u and ppc-aix-stage-9 into jdk9 repository. That's fine for us:)
With best regards,
Volker
On Tue, Dec 3, 2013 at 5:48 PM, <mark.reinhold at oracle.com> wrote:
> 2013/12/2 17:37 -0800, volker.simonis at gmail.com:
>> if I understand this right, there's another downside of the approach
>> you propose: you can't easily downport changes from JDK9 to JDK8
>> update releases. This is because changes in JDK9 (i.e. our
>> ppc-aix-port) will have ancestor changes in JDK9 which are not in JDK8
>> (i.e. they are there, but they are different changes with the same
>> content because they have been imported and not pulled into JDK9).
>>
>> So what will be the best way to downport something from JDK9 to JDK8.
>> The only possiblity I see is again to "cherry pick"; i.e., export the
>> change from JDK9 and import it into JDK8. Do you see other
>> possibilities?
>
> No, but as Alan said, we already do this all the time from JDK 8
> to the JDK 7 updates. It's really not that hard -- the hg import
> and export commands take care of most of the details.
>
> - Mark
>
>
> P.S. It's "JDK 8" and "JDK 9". Note the space after the "K".
More information about the ppc-aix-port-dev
mailing list