JDK 8 updates process: jdk8u-dev and jdk8u forests, fix versions, fix approval process

Andrew Haley aph at redhat.com
Fri Feb 22 16:04:41 UTC 2019

On 2/22/19 3:31 PM, Langer, Christoph wrote:

> We’ll use the jdk8u-fix-request/jdk8u-fix-yes (or no?) process as in
> jdk11, correct? I thought so by reading the previous mail threads
> and hence added the request label to all items where push approval
> has been asked for in the last 2 days. Hope that was ok ��

Yes. As we discussed, there should be no difference in this process
from later updates.

> The latest pushes to jdk8u-dev (which date back a few days) indicate
> that the fix version that hgupdater uses when handling pushes to
> jdk8u-dev is “openjdk8u”. I understand that the request has been
> made to add the fix version “openjdk8u211” to JBS and to use it for
> jd8u-dev by hgupdater. Is that correct?


> Can you please communicate once “openjdk8u211” is available?

As soon as I get the message.

> If you agree, I would fix the existing “openjdk8u” backport issues
> to set their fix version to “openjdk8u211” once the latter is
> available. That way it’ll be clearer for people that search in the
> JBS system in which OpenJDK update they should expect their
> fixes. Ok?


> Furthermore, I have the understanding that all open fixes should now
> be pushed to jdk8u-dev until we reach a state when all is in and we
> can merge/copy into jdk8u. Correct?

For now, yes. I'll let the list know when the time has come to close

Andrew Haley
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671

More information about the jdk8u-dev mailing list