[11u]: 8u222 & 11.0.4 release schedule
aph at redhat.com
Sun May 19 16:44:45 UTC 2019
On 5/3/19 2:15 PM, Lindenmaier, Goetz wrote:
>> But otherwise, the intent here is for people to start aiming their
>> work at the next release at rampdown. Patches being pushed to
>> jdk11u should be rare.
> I think we should use jdk11u only for rampdown. So patches pushed to
> jdk11u should be limited and well restricted, but not necessarily
> rare. But yes, definitely less than pushed to jdk11u-dev.
I have to agree with Andrew here. We should minimize churn at
rampdown: every patch and combination of patches risks undermining
stability, and that's true even with apparently low-risk
patches. There were a lot of patches pushed to jdk11 during rampdown
last time around, and that isn't necessarily good.
>> The master tree (jdk11u) is snapshots for people to test and integrate
>> downstream, leading up to the final release.
>No. The jdk11u is a repository used for rampdown so that development
>can be continued in another repository, here jdk11u-dev.
>It is not a convenience for testers, it is to allow parallel work with
>two different intentions: development <--> stabilization.
Both of these can be true: Andrew is talking about what 11u is, you
are talking about what it is for.
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671
More information about the jdk-updates-dev