JDK8u212 next steps

[Langer, Christoph]

Hi,

I've transported the changes for OpenJDK 8u212 to the jdk8u repository forest, as per the steps below. The request for a new JBS release "openjdk8u222" was sent to ops.

As of now, changes that are targeted for jdk8u212 need to be pushed to jdk8u. Those must, of course, have been labeled with "jdk8u-critical-request" and approved beforehand. I've set  "jdk8u-critical-request" on bugs JDK-8220641, JDK-8193764 and JDK-8189761 as I assume they shall go into jdk8u. Please correct it in JBS if my assumption is wrong.

Approvals & pushes for openjdk8u222 will have to wait until the new setup for jdk8u-dev is in place. I'll send an update once this is available.

Best regards
Christoph


From: Langer, Christoph
Sent: Freitag, 15. März 2019 22:33
To: jdk8u-dev at openjdk.java.net
Subject: JDK8u212 next steps

Hi,

we have reached a state where the list of required jdk8u backport items [0] is in jdk8u-dev. Thanks to all contributors for their hard work!

When there are no objections, I'll do the push to jdk8u on Monday. In detail this will mean the following steps:
1. merge the repos jdk8u-dev -> jdk8u
2. tag jdk8u with "jdk8u212-b01"
3. tag jdk8u-dev  with "jdk8u222-b00"
4. merge "jdk8u212-b01" back into to jdk8u-dev
5. request ops on behalf of the project lead to create version "openjdk8u222" in JBS and set up hgupdater to honor this version for pushes to jdk8u-dev

I'll communicate when this work is finished. After that, jdk8u-dev will collect fixes for OpenJDK 8u222 and critical fixes can be requested to be pushed to jdk8u for 8u212 using the jdk8u-critical-request label.

Best regards
Christoph

[0] https://bugs.openjdk.java.net/issues/?filter=36394