[11u]: 8u222 & 11.0.4 release schedule

[Andrew John Hughes]

On 29/04/2019 15:22, Lindenmaier, Goetz wrote:
> Hi Andrew, 
> 
> yes, this is the same as what I tried to phrase.
> 
> Just one thing: you are mentioning RDP1.
> How do you want to handle this?
> Will we announce that only P1-P3 bugs (no P4,P5, 
> no enhancements of priority P1-P5) may be pushed
> to jdk11u-dev starting tomorrow?  
> This is what https://openjdk.java.net/jeps/3 is saying
> and how jdk development is handled.
> 
> Or should we just say jdk11u-dev is open for development,
> i.e., any changes, until RDP2? And leave out mentioning 
> RDP1.
> 
> Best regards,
>   Goetz.
> 
> 
> 

That's a good point and a case of bad terminology on my side :(
I used "RDP1" because we were already talking about RDP2, without really
thinking of the implication. Because I've been focused on the last
release until the last week or so, I'm still very much of the frame of
mind that we are still relatively early in the next releases and it
wasn't my intention to suggest we'd be locking things down so soon.

The update projects differ from the main JDK project in a number of
ways: they have half the life span (three months rather than six), all
changes require explicit approval as well as review, and the very nature
of an update release means that it isn't the place for major new
features. Hence, I'm not sure the priority matrix in JEP3 really makes
much sense in our context, as a maintainer can choose to block a
particular fix anyway, and, in many cases, the original priority will
have been determined by someone other than the backporter.

Hence, I would prefer a simpler three stage structure - development,
rampdown and freeze - which is what was in my mind when I wrote the
previous schedule (if not the terminology).

So, for clarity:

March 2019: jdk11u-dev repo open (tag: jdk-11.0.4+0)
=============== 11.0.3 Released ============================
=     jdk11u tree gets changes by merge from jdk11u-dev    =
============================================================
Wednesday, May 01 2019: First build (tag: jdk-11.0.4+1)
Wednesday, May 08 2019: Second build (tag: jdk-11.0.4+2)
Wednesday, May 15 2019: Third build (tag: jdk-11.0.4+3)
Wednesday, May 21 2019: Fourth build (tag: jdk-11.0.4+4)
Wednesday, May 29 2019: Fifth and final dev build (tag: jdk-11.0.4+5)
================= Rampdown =================================
= jdk11u tree gets changes only by jdk11u-critical-request =
============================================================
Wednesday, June 5, 2019: First rampdown build (tag: jdk-11.0.4+6)
Wednesday, June 12, 2019: Second rampdown build (tag: jdk-11.0.4+7)
Wednesday, June 19, 2019: Third rampdown build (tag: jdk-11.0.4+8)
Wednesday June 26 2019: Last tag before code freeze (tag: jdk-11.0.4+9)
================= FREEZE ===================================
=            jdk11u sees no public changes                 =
============================================================
Tuesday, July 16 2019: GA (tag: jdk-11.0.4-ga, likely to be jdk-11.0.4+10)

So, we could probably start the post-release stage a week earlier in
future i.e. the Wednesday of the week after the CPU, if we're happy with
the same stable process.

Best regards,
-- 
Andrew :)

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

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