Future jdk9u updates & 9-critical-request
aph at redhat.com
Thu Feb 8 10:26:09 UTC 2018
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.
> They can then use the push approval process to contribute the
> corresponding changes back.
You're missing the point. The last release of jdk9u was not fit for
purpose because it broke two targets, and the maintainers of those
targets were not given time to fix them. When a release is made it's
not just an Oracle release, it's an OpenJDK release, and the release
manager should be aware of that.
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 jdk-updates-dev