JDK 11.0.3 Update process

[Andrew Hughes]

On Fri, 15 Feb 2019 at 13:44, Andrew Haley <aph at redhat.com> wrote:
>
> On 2/15/19 1:32 PM, Langer, Christoph wrote:
>
> > So, I suggest the following process when creating jdk11u-dev (The
> > Andrews/Redhat need to confirm whether it fits for them...)
> >
> > 1. Close the jdk11u repository for commits (only the maintainers of
> > jdk11 should have push authority).
>
> Let's not. There's more of a risk that we get stuck on something
> urgent for lack of a maintainer to push than there is of unauthorized
> committers pushing bad patches. Committers can be trusted.

As I said before [0], I think the jdkxxu repository should be restricted,
maintaining a clear distinction between a jdkxxu-dev branch for developers
to commit to, and the jdkxxu for consumption. The latter is the one that
would be frozen and used as the base for releases around CPU time.
That avoids a situation where people push stuff to jdkxxu in the interim
and then are surprised when it's not in the release.

If there's an issue with a lack of a maintainer, then that's a sign we
need to appoint more, not abandon the whole idea.

That said, I think it's too early to be branching for 11.0.4, especially given
processes are still in a state of flux. I'd expect that more around mid-March.

[0] https://mail.openjdk.java.net/pipermail/jdk-updates-dev/2019-February/000416.html
-- 
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