JDK 11.0.3 Update process

[Langer, Christoph]

Hi,

> 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.

That's exactly my point of view.

> 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.

For jdk11 updates, the SAP team is definitely willing to help.

> 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.

Sounds reasonable. Nevertheless, we should start the work to get the repos and the infrastructure (e.g. fix version labeling) set up now to get a smooth process for 11.0.3 delivery.

Best
Christoph