JDK 11.0.3 Update process

Langer, Christoph christoph.langer at sap.com
Tue Feb 19 14:07:42 UTC 2019


Hi Rob,

> > Besides that, I have another question which I kindly ask Rob to answer :)
> >
> > > In addition to this I would like to request that the fix versions for
> > > hgupdater be set to:
> > >
> > > jdk-updates/jdk11u-dev: 11.0.4
> > > jdk-updates/jdk11u: 11.0.3
> >
> > Once this is done, how best proceed with a change (say a P1) which
> > needs to go into both 11.0.3 and 11.0.4. My idea was to downport it
> > directly to jdk-updates/jdk11u and regularly push from
> > jdk-updates/jdk11u to jdk-updates/jdk11u-dev. Is this the way it was
> > previously done at Oracle?
> 
> No, we always push to the always-open repo first. (in this case the
> 11.0.4 repo) After examining the risk of the fix / impact to testing, if
> an issue is approved for the rampdown release it is hg export / imported
> to that repo.


Interesting. Can you tell how the hgupdater tool reacts to merges? 

a) If you merge 2 repositories and both contain a fix for the same bug (that is, JBS backport items exist) - will hgupdater just ignore the incoming changeset? Or will an additional JBS backport item be created?
b) Imagine the following situation: repository jdk11u is set up for 11.0.3 fixes and jdk11u-dev is set up for 11.04. jdk11u contains a fix for issue A and hgupdater had created a JBS backport item for 11.0.3. At the moment we'd merge back 11u -> 11u-dev the fix for A will land in 11u-dev. Would hgupdater then create an 11.0.4 backport item?

Thanks
Christoph



More information about the jdk-updates-dev mailing list