[11u]: 8u222 & 11.0.4 release schedule

[Langer, Christoph]

> -----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:
> 
> During RDP1:
> 
> 1. Tag in jdk8u-dev/jdk11u-dev
> 2. Pull into jdk8u / jdk11u
> 
> 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,

Ah, I see. So, yes, we're in full understanding and agreement then. ��

/Christoph