8u/11u repo access and Jira changes

Langer, Christoph christoph.langer at sap.com
Tue Feb 26 21:40:34 UTC 2019

Hi Andrew,

> The questions I really need answers to are:
> 1. Who is going to push from jdk8u-dev -> jdk8u?

The maintainers (you, Aleksey, me, Goetz, ...)

> 2. What is the frequency of these pushes going to be?

Ok, again, here's our proposal (from the SAP folks):

We sync once per CPU release cycle from jdk8u-dev -> jdk8u, respectively from jdk11u-dev to jdk11u. For jdk11u, we've kind of done it now by the creation of the jdk11u-dev repo. For jdk8u I propose to do the initial push to jdk8u once all open Oracle backports were integrated.
Then, I expect a few pushes to jdk8u/jdk11u and we'll tag these once in a while like jdk-11.0.3+1 etc. These tags will be integrated back to dev regularly (by those who set the tags, that is, the maintainers).
At the release day, you'll sync your security work on top of jdk8u/jdk11u and add a final jdk-11.0.3+xx tag and the jdk-11.0.3-ga tag (which should point to the same change). And this will be integrated back to jdk11u-dev.

What do you think of that?

> 3. What testing is going to be performed prior to these pushes?

Good question, currently I guess it's our quality testing at SAP plus whatever you have at RedHat. We should eventually get to something better, e.g. have some open test results from AdoptOpenJDK...??

> I'd prefer regular pushes with tags, because that would help us
> downstream (aarch64-port/jdk8u-shenandoah,
> shenandoah/jdk11) in being able to integrate changes more frequently.
> Under Oracle, we've had to do that at GA time only.

That should be helped with our concept.

Best regards

More information about the jdk8u-dev mailing list