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

[Rob McKenna]

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.

    -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
>