JDK 11.0.3 Update process

[Lindenmaier, Goetz]

Hi,

well, should have condensed this into one mail ... but nevertheless ...
> I didn't say there was anything the matter with it, more that I was
> surprised it was happening so quickly. I'm still wrapping up things from
> the last CPU.
Guess my other mail explains why we want to engage now.  We want to
release SapMachine as close to 4/15 as possible, and with the same set
of changes as you.

> From experience, the earlier you split off a release branch, the more
> work has to be done in backporting from the current development branch
> to the release branch, or, as you suggest, pulling from the release branch
> back into the development branch.
I don't think the pulling is that much work, but letting the fixes soak makes
sense.

> On that latter approach, there's an obvious risk there that you push something
> to 11.0.3 first which causes issues. I think there are good reasons for only
> determining fixes as worthy for the release branch after they've soaked for
> some time in the development branch. It's also not clear to me what the
> "RDP2 rules" are.
https://openjdk.java.net/jeps/3 
This explains what changes may be pushed in which phase.
We could reuse that.

> I would like to see regular tags for both 8u & 11u. This would help testing
> of our downstream trees, which currently don't get merged until Oracle push
> all their internal work after release.
Yes.  Tags would be great.  I would appreciate weekly builds tags in jdk11u after rdp2,
11.0.3-rdp2 when last jdk11u-dev is pulled to jdk11u, 
11.0.3-rdp1 when you (and us)  snapshot the tree,
11.0.3-ga in the end.

Cheers,
  Goetz.

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