[11u]: 8u222 & 11.0.4 release schedule

[Lindenmaier, Goetz]

Hi,

OK, as the majority seems to agree, let's push the 
split between jdk11u-dev and jdk11u to 28.5.2018.

> During RDP1:
> 1. Tag in jdk8u-dev/jdk11u-dev
> 2. Pull into jdk8u / jdk11u 
I would like to express this differently though.
I would not announce that we tag in jdk11u-dev and later in jdk11u.
This can be confusing.
I would phrase this differently: 
"From 1.5  to 28.5 merges from jdk11u-dev to jdk11u will be done
 weekly before tagging jdk11u."
Or better:
"Before RDP2, merges from jdk11u-dev to jdk11u will be done 
 weekly before tagging jdk11u."
Then, tags are always done in jdk11u, and then merged to jdk11u-dev.

Also, we need to state that jdk11.0.5 development only starts on 29.5.2019.
Else, it would have started 2.5.2019.  

And, do I understand correctly, you want to enforce RDP1 restrictions 
on both repos starting 1.5.2019? That would mean you can not push
enhancements to jdk11u at all for four weeks!  
https://openjdk.java.net/jeps/3

Best regards,
  Goetz.










> -----Original Message-----
> From: Andrew John Hughes <gnu.andrew at redhat.com>
> Sent: Freitag, 26. April 2019 19:25
> To: Langer, Christoph <christoph.langer at sap.com>
> Cc: Severin Gehwolf <sgehwolf at redhat.com>; 'jdk8u-dev at openjdk.java.net'
> <jdk8u-dev at openjdk.java.net>; Andrew Haley <aph at redhat.com>; Aleksey
> Shipilev <shade at redhat.com>; jdk-updates-dev at openjdk.java.net;
> Lindenmaier, Goetz <goetz.lindenmaier at sap.com>
> Subject: Re: [11u]: 8u222 & 11.0.4 release schedule
> 
> 
> 
> On 26/04/2019 18:10, Langer, Christoph wrote:
> 
> snip..
> 
> >
> > I don't fully get your point here... so, are you saying we should also tag in
> jdk8u/jdk11u vs jdk8u-dev/jdk11u-dev until RDP2?
> >
> > The former has the disadvantage that there's some more merging back and
> forth and we'll probably see more merge changesets...
> >
> > Or do you mean to say something else? ��
> >
> > Thanks
> > Christoph
> >
> 
> I was agreeing with what I interpreted you to be saying, which I believe
> was:
> 
> 
> and thus the tag will be in both repositories.
> 
> In RDP2:
> 
> 1. Tag in jdk8u / jdk11u
> 2. Pull into jdk8u-dev / jdk11u-dev
> 
> with again the end result being that the tag is in both repos.
> 
> During both stages, someone not involved in development can ignore
> jdk8u-dev & jdk11u-dev and just pull each new tag from jdk8u & jdk11u
> for builds & testing.
> 
> I think that keeps things simpler for downstreams who primarily want to
> consume the results rather than participate in their production.
> 
> Hope that's clearer,
> --
> Andrew :)
> 
> Senior Free Java Software Engineer
> Red Hat, Inc. (http://www.redhat.com)
> 
> PGP Key: ed25519/0xCFDA0F9B35964222 (hkp://keys.gnupg.net)
> Fingerprint = 5132 579D D154 0ED2 3E04  C5A0 CFDA 0F9B 3596 4222
> https://keybase.io/gnu_andrew