JDK 11.0.3 Update process

[Lindenmaier, Goetz]

Hi Andrew, 

> It does seem a bit early to me for 11.0.4, especially with the
> transition from Oracle ownership. I was expecting
> the branch to happen more around the time we received the security
> patches, but then I also feel that the lead
> time under Oracle was too long, leading to patches taking a long time
> to actually appear in releases. It really
> depends on what testing one wants to do prior to release.

what we are proposing is to use jdk11u-dev for 11.0.4, and jdk11u for 
11.0.3 as soon as both are available.

What is the matter with doing this right now?  Not doing it means
that all changes downported will still end up in 11.0.3.  
Actually, I think 11.0.3 should be in stabilization phase currently, 
and it should go there as soon as possible. Aleksey and Christoph
are currently building a repository that resembles 11.0.3-oracle
as good as possible.  We should stabilize this repository starting right 
when they are finished.

At the same time, we should not block others from downporting 
changes needed in 11, but not necessarily in 11.0.3. 
There are already some 30 changes flagged 11.0.4-oracle. We could
start pushing them to jdk11u-dev if we dedicate the two repos for the
two different releases. And I think doing that now would be better than 
starting this business only 8 weeks in advance of the release.
(And if Christoph does not volunteer to do that, I might :))

So, to take up what Volker is proposing, and to put it into my own words,
I would propose:

Once we have jdk11u-dev:
 * let's start pushing 11.0.4-oracle changes to jdk11u-dev.
 * let's continue pushing 11.0.3-oracle changes to jdk11u.
 * let's push changes requested for downport for jdk11u to jdk11u-dev except:
 * let's push changes that fix issues in 11.0.3 that adhere to the RDP2 rules
    to jdk11u. This can be both: downports and fixes crafted for 11.0.3
and finally:
  * on every Thursday (or any other weekly point in time), let's merge all changes
     from jdk11u to jdk11u-dev except if jdk11u has a major issue.
     (I would volunteer to do this for now) )(based on a change that ran through
      our nightly testing as long as there are no build tags)

Best regards,
  Goetz.






> 
> Thank you for the nomination, by the way. Accepted :-)
> --
> 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