JDK 11.0.3 Update process

[Andrew Hughes]

On Tue, 19 Feb 2019 at 09:40, Andrew Haley <aph at redhat.com> wrote:
>
> On 2/18/19 10:49 PM, Andrew Hughes wrote:
> > Indeed. In the Oracle sense, it is very much the former role of
> > adjudicating on which changes make it to the release and which don't.
> >
> > The other role has been largely nameless, because that process is
> > basically opaque under Oracle ownership; once they branch the tree
> > (privately) for "RDP2", the only evidence we have of activity is entries
> > in the bug database.
> >
> > So this is the area we really need to define more in-depth. At the
> > end of day, primary responsibility will have to go to someone who
> > can do TCK testing as any release should pass that. On what
> > platforms that is the case is yet another issue, so the work may
> > need to be distributed against multiple interested parties.
>
> Probably, yes. But we have to be clear what exactly is meant by
> "primary responsibility". From context I believe you're talking about
> responsibility for doing the patch integration into the release
> branch. And yes, they have to do TCK testing.
>

I'm talking not so much about individual patch integration, but the process
of tagging and making a release i.e. deciding that it is good to go.

> > OpenJDK 6 & 7 have been much lower traffic, so we have generally got
> > away with doing our Red Hat builds and TCK testing, and then just
> > doing the final push & release in public. The process will need to
> > be formalised for 8u & 11u.
>
> I'm reluctant. The problem with formalizing process even more is that
> it becomes incomprehensible to anyone except the two or threee people
> working on a release full time.

Ok, let's put it another way; the next security update is on 2019-04-16.
I need to know about a month before then whether I'm following the
same process as for 7 (snapshot the tree, apply security patches,
push them after unembargo and follow up with a release), or if we're
doing something different, or if someone else is doing this.

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



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