8u222 release schedule

[Langer, Christoph]

<snip>
 
> It's not clear to me what the difference is between 'branch jdk8u-dev'
> and RDP2. I thought they were the same thing.
> 
> So my impression is that the process for release x goes as follows:
> 
> 1. jdk8u is tagged jdk8ux-b00
Yes.

> 2. Initial work on jdk8ux takes place in jdk8u-dev tree
Yes.

> 3. Each Wednesday, jdk8u-dev is merged to jdk8u and tagged with the next
> incremental build number.
Nope, there would be only one merge jdk8u-dev->jdk8u, as stated in the timeline. After that, fixes targeted for jdk8u would have to be done in jdk8u. The weekly merge then goes the other way jdk8u->jdk8u-dev.

> 3. At RDP2, weekly merges cease and fixes for jdk8u have to be
> explicitly requested by jdk8u-critical-request. jdk8u-dev moves on to
> release x+1.
Nope, as stated above. RDP2 in that case would probably only mean some more restricted criteria for allowing fixes into jdk8u. But jdk8u-critical-request will be needed for each push into jdk8u, starting from the initial merge jdk8u-dev->jdk8u.

> 4. At code freeze, no more changes are made to jdk8u publicly until
> after 13h00 PT (20h00 UTC Apr/Jul/Oct, 21h00 UTC Jan) on the unembargo
> date when the embargo is lifted. The security fixes are then reviewed
> and pushed, including the final tag jdk8ux-ga.
Yes.

> 5. Return to #1 for x+1.
Yes.

So, however, let's wait for the outcome of the discussion in [0]. Maybe we end up moving the jdk8u-dev->jdk8u to the RDP2 date, unless somebody seconds Goetz with good arguments.

Maybe in the end, Andrew (aph) needs to make a decision ��

Best regards
Christoph

[0] https://mail.openjdk.java.net/pipermail/jdk-updates-dev/2019-April/001004.html