JDK 11.0.3 Update process

[Lindenmaier, Goetz]

> 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.
@Rob
OK, so is that the reason we see so many redundant changes once the
security fixes are pushed to the open?
And why did you choose to do it differently with a new release (jdk12) 
and jdk/jdk?
@Andrew  
I'm not sure this is desirable ... It means considerable work (what 
Aleksey and Christoph are doing needs to be done twice!) and 
the two repos might look quite differently ...

Best regards,
  Goetz. 



> 
>     -Rob
> 
> >
> > The other possiblity would be to instantly downport it to both
> > jdk-updates/jdk11u and jdk-updates/jdk11u-dev. But in the end, this
> > would leave us (after 11.0.3 will be merged back into
> > jdk-updates/jdk11u) with two different instances of the same change in
> > jdk11u-dev and all subsequent releases. I think that would be not very
> > nice and quite confusing. If possible I'd like to avoid that.
> >
> > Thanks for your support,
> > Volker
> >
> > On Mon, Feb 18, 2019 at 6:01 PM Andrew Haley <aph at redhat.com> wrote:
> > >
> > > On 2/18/19 4:22 PM, Rob McKenna wrote:
> > > > Correct me if I have the wrong fix versions here, but the following email
> > > > should suffice for both requests:
> > >
> > > Thanks. I'll wait for an ACK from someone else contributing to this
> discussion,
> > > then send the request.
> > >
> > > --
> > > Andrew Haley
> > > Java Platform Lead Engineer
> > > Red Hat UK Ltd. <https://www.redhat.com>
> > > EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671