[11u]: 11.0.4 release schedule
Andrew John Hughes
gnu.andrew at redhat.com
Wed Apr 24 16:02:49 UTC 2019
[Bringing jdk8u-dev into this as well as there's a lot of common material]
On 24/04/2019 16:08, Langer, Christoph wrote:
> Hi,
>
>> On 4/24/19 11:01 AM, Aleksey Shipilev wrote:
>>> On 4/24/19 11:47 AM, Langer, Christoph wrote:
>>>> I've now published the following schedule for 11.0.4 on the Wiki [0]:
>>>>
>>>> March 2019: jdk11u-dev repo open (tag: jdk-11.0.4+0)
>>>> Tuesday, April 30 2019: Branch jdk11u-dev to jdk11u
>>>> Wednesday, May 1 2019: First build (tag: jdk-11.0.4+1)
>>>> Wednesday, May 29 2019: RDP2
>>>> Wednesday June 26 2019: Last tag before code freeze
>>>> Tuesday, July 16 2019: GA (tag: jdk-11.0.4-ga)
>>>>
>>>> Is everyone in agreement with that?
>>>>
>>>> Note: It means that we'll branch next week from jdk11u-dev to jdk11u!
>>>
>>> That also means outstanding 11.0.4-oracle things are better to get to 11u-
>> dev within a week, right?
>>> https://bugs.openjdk.java.net/issues/?filter=36409
>>>
>>> I have my doubts about having 2.5 months gap between fork and release.
>> That feels too early. Or
>>> maybe not, given there is a pending 13 freeze in between, and also
>> summer vacations.
>>
>> That feels early to me too. What will happen is a ton of jdk11u-critcial-
>> requests
>> for trivial bugs, simply to get them into the next release.
>
> Well, I had discussions with Goetz about this... I also have/had the feeling, that the proposed date to do the branch is too early. I would also rather propose to do the jdk11u-dev -> jdk11u transport at about the date mentioned as RDP2 above.
>
> I think, Goetz' reasoning behind suggesting the early branch is, if there was some late checkin which destabilizes things, there would only be about 4 weeks to get it fixed when branching late. Oracle also has an early branch/RDP2 date for their updates. E.g. 12.0.2 is probably branched about now.
>
> 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)
>
> So, I guess we shall wait a bit and collect further comments on this, e.g. from Goetz himself. Depending on the outcome of the discussion I'd update the Wiki at the end of the week.
>
> Best regards
> Christoph
>
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.
--
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
More information about the jdk-updates-dev
mailing list