> Iris -- As you create the initial JDK 9 forest, please tag the tip of each
> repository with "jdk9-b00". That will make it easy to identify the point at
> which the JDK 9 code line forked from JDK 8. Thanks.
Ok.
iris
2013/12/2 7:36 -0800, mark.reinh...@oracle.com:
> ...
>
> To simplify the release-endgame process, I hereby make the following
> proposal:
>
> 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
Sounds reasonable to me.
-Joe
On 12/02/2013 03:36 PM, mark.reinh...@oracle.com wrote:
The rate of change in JDK 8 is ramping down, and the JDK 9 forests will
be open soon. Until JDK 8 ships, how shall we manage changes that need
to go into both releases?
The general rule, of course, is that c
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-
2013/12/2 22:50 -0800, chris.hega...@oracle.com:
> Provided that engineers forward port JDK8 changes to JDK9 in a timely
> manner, then 'hg import --exact' can be used. Since JDK9 will contain
> the parent change set. That way tag changesets could also be forward
> ported, when 'hg import --exact'
2013/12/2 17:37 -0800, volker.simo...@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
On 2 Dec 2013, at 23:36, mark.reinh...@oracle.com wrote:
> ...
>
> By "apply independently" I mean "cherry pick"; i.e., export the patch
> for the JDK 8 changeset, apply the patch to a JDK 9 working forest,
> adjust the result as needed, build and test, and then commit a new
> changeset to JDK 9
On 03/12/2013 09:37, Volker Simonis wrote:
:
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?
We do this all the time when bringing
Hi Mark,
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
The rate of change in JDK 8 is ramping down, and the JDK 9 forests will
be open soon. Until JDK 8 ships, how shall we manage changes that need
to go into both releases?
The general rule, of course, is that changes should go into the current
development release first, where they can "soak" through
10 matches
Mail list logo
