[11u]: 8u222 & 11.0.4 release schedule

[Langer, Christoph]

Hi Andrew,

<snip>

> >>> March 2019: jdk11u-dev repo open (tag: jdk-11.0.4+0)
> >>> ================= RDP1
> =====================================
> >>> =     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 RDP1 build (tag: jdk-11.0.4+5)
> >>> ================= RDP2
> =====================================
> >>> = jdk11u tree gets changes only by jdk11u-critical-request =
> >>>
> ==========================================================
> >>> ==
> >>> Wednesday, June 5, 2019: First RDP2 build (tag: jdk-11.0.4+6)
> >>> Wednesday, June 12, 2019: Second RDP2 build (tag: jdk-11.0.4+7)
> >>> Wednesday, June 19, 2019: Third RDP2 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)
> >>>
> >>> This allows regular testing earlier in the cycle, but without
> >>> restricting the process down to critical fixes early.
> >>
> >> Sounds like a good suggestion to me as I can see the need to have EA
> builds early.
> >> I think technically we should then tag in jdk11u-dev/jdk8u-dev until the
> 29th of May and pull these tags into jdk11u/jdk8u.
> >> We'll have to confirm with ops whether this will correctly resolve the bugs
> in JBS (e.g. with the right build associated).
> >
> > +1
> >
> > Thanks,
> > Severin
> >
> 
> That sounds sensible. My primary concern is that something is available
> and tagged in 8u/11u for people not necessarily active in development to
> consume and test, perhaps first integrating into downstream repositories
> as we do with our Shenandoah repositories.

I don't fully get your point here... so, are you saying we should also tag in jdk8u/jdk11u vs jdk8u-dev/jdk11u-dev until RDP2?

The former has the disadvantage that there's some more merging back and forth and we'll probably see more merge changesets...

Or do you mean to say something else? ��

Thanks
Christoph