[11u]: 11.0.4 release schedule

[Severin Gehwolf]

On Thu, 2019-04-25 at 06:24 +0000, Langer, Christoph wrote:
> Hi,
> 
> > On 24/04/2019 16:08, Langer, Christoph wrote:
> 
> <snip>
> 
> > > But I would be fine with changing the schedule to this:
> > > 
> > >      March 2019: jdk11u-dev repo open (tag: jdk-11.0.4+0)
> > >      Tuesday, May 28 2019: RDP2, Branch jdk11u-dev to jdk11u
> > >      Wednesday, May 29 2019: First build (tag: jdk-11.0.4+1)
> > >      Wednesday June 26 2019: Last tag before code freeze
> > >      Tuesday, July 16 2019: GA (tag: jdk-11.0.4-ga)
> > > 
> > 
> > This looks better.
> > 
> > The addition I'd like to see is to start the weekly promotions earlier,
> > so they also happen in the first stage. That would avoid b01 being so
> > huge. I think that's a good halfway house between proposing entering the
> > critical fix stage next week and not promoting anything until the end of
> > May.
> > 
> > That would mean multiple jdk11u-dev->jdk11u & jdk8u-dev->jdk8u merges
> > from next Wednesday 1st of May through to the final one of May 29:
> > 
> > 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