Future jdk9u updates & 9-critical-request

[Andrew Hughes]

On 8 February 2018 at 10:26, Andrew Haley <aph at redhat.com> wrote:
> On 07/02/18 16:33, dalibor topic wrote:
>
>> In short, someone is likely always going to be able to claim that a
>> given release is broken for them in one way or another.
>
> This shouldn't happen if a proper release process is followed.
> This wasn't a minor problem: two targets didn't even run.
>

I'm not a HotSpot developer, and certainly not an AArch64 expert,
but it was pretty obvious to me from a casual inspection of the
problem changeset that support for these targets was absent.
It's also not the first time a target has been broken by a CPU,
though it is the first time for AArch64 being part of an upstream
release.

There was a changeset that fixed this for the PPC targets, which
aren't handled by Oracle, as far as I'm aware. So whatever
process was used there needs to be expanded to cover other
ports. Hopefully the vulnerability group will resolve this.
-- 
Andrew :)

Senior Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)

Web Site: http://fuseyism.com
Twitter: https://twitter.com/gnu_andrew_java
PGP Key: ed25519/0xCFDA0F9B35964222 (hkp://keys.gnupg.net)
Fingerprint = 5132 579D D154 0ED2 3E04  C5A0 CFDA 0F9B 3596 4222