[8u-communication] JDK 8u60 released today! (and 8u72 timeline)

[Andrew Hughes]

----- Original Message -----
> Approved changesets are available in the always open forest so
> reproducing the state of a post-rdp2 release shouldn't be very difficult.
> 
> Any fixes that go into a release post-RDP2 will have a corresponding JBS
> backport. If you search JBS for a fixVersion of 8uXX (and a resolved in
> build value >= to the RDP2 build) you'll see a list of fixes approved
> for that release.

Ok, so let me see if I understand this correctly.

If I want to re-create, say, jdk8u66-b03, I would have to check out
jdk8u66-b02 from http://hg.openjdk.java.net/jdk8u/jdk8u and friends,
then go through the OpenJDK bug database and find every bug that
was fixed in jdk8u66-b03 (e.g. [0]), then find out what the original
bug ID is for each one, then backport all the changesets?

Then, for jdk8u66-b04, I have to do the same again and so on.

This seems unnecessarily convoluted and prone to error. Why not just
make the trees available as before?

[0] https://bugs.openjdk.java.net/issues/?jql=project%20%3D%20JDK%20AND%20status%20%3D%20Resolved%20AND%20%22Resolved%20In%20Build%22%20in%20%28b02%2C%20b03%29%20AND%20fixVersion%20%3D%208u66%20ORDER%20BY%20priority%20DESC

> 
>     -Rob
> 
> On 04/09/15 22:21, Omair Majid wrote:
> > Hi Rob,
> >
> > * Rob McKenna <rob.mckenna at oracle.com> [2015-08-19 13:26]:
> >> Some folks may be wondering how they get fixes pushed into 8u66 so
> >> just to reiterate, all you have to do is follow the critical approval
> >> process [1] and the maintainers will take care of the rest!
> >
> > I am hoping I am misreading or misinterpreting some of this because it
> > sounds to me like you are saying that the community can't see what fixes
> > a future 8uXY release contains until it is tagged and released on the
> > day of the release (which coincides with the day of the CPU). What I
> > understand is that we can still ask for changesets to be backported but
> > we can't actually see/test/fix the 8u66 trees until a release is "done"?
> > And the same will happen for the 8u72 release after this October so we
> > can't see/test/fix what-really-is-8u72 ether after October?
> >
> > Is that right?
> >
> > Thanks,
> > Omair
> >
> 

-- 
Andrew :)

Senior Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)

PGP Key: ed25519/35964222 (hkp://keys.gnupg.net)
Fingerprint = 5132 579D D154 0ED2 3E04  C5A0 CFDA 0F9B 3596 4222

PGP Key: rsa4096/248BDC07 (hkp://keys.gnupg.net)
Fingerprint = EC5A 1F5E C0AD 1D15 8F1F  8F91 3B96 A578 248B DC07