[FREEZE] 11.0.3 NOW FROZEN

[Langer, Christoph]

Hi,

Andrew Hughes, as the maintainer of the CPU forest, has let us know that he can/will pull a final public tag (11.0.3+6) in jdk11u until 6PM UTC today.

To clean up the current situation, Goetz and me will push the backout change for the accidental JDK-8207760 [0] commit and then tag 11.0.3+6. @Andrew Haley: Can you please confirm this by approving the backout bug JDK-8221769 [1] with jdk11u-critical-yes?

Thanks & Best regards
Christoph
 
[0] http://hg.openjdk.java.net/jdk-updates/jdk11u/rev/22cfec306339
[1] https://bugs.openjdk.java.net/browse/JDK-8221769 

> -----Original Message-----
> From: jdk-updates-dev <jdk-updates-dev-bounces at openjdk.java.net> On
> Behalf Of Severin Gehwolf
> Sent: Dienstag, 2. April 2019 10:31
> To: Aleksey Shipilev <shade at redhat.com>; Andrew John Hughes
> <gnu.andrew at redhat.com>; 'jdk-updates-dev at openjdk.java.net' <jdk-
> updates-dev at openjdk.java.net>
> Subject: Re: [FREEZE] 11.0.3 NOW FROZEN
> 
> On Tue, 2019-04-02 at 10:00 +0200, Aleksey Shipilev wrote:
> > On 4/2/19 3:22 AM, Andrew John Hughes wrote:
> > > There are two changes in the repository after 11.0.3+5 [1] [2]. These
> > > changes were not committed until after the agreed deadline of the 1st
> > > and so will now have to wait until 11.0.4.
> >
> > That would be very confusing, as [1] is recorded to be in 11.0.3 in JIRA now,
> in addition to being
> > in repository history as between 11.0.3+5 and 11.0.3+6. Either revert the
> patches after 11.0.3+5 and
> > let us push to 11.0.4, or pull the patches into 11.0.3 CPU.
> 
> As I understand it, it's only [1] which we'd be talking about. [2]
> apparently got pushed to jdk-updates/jdk11u by accident[*]. Revert is
> in progress.
> 
> +1 to cleaning jdk-updates/jdk11u up/re-tagging as Aleksey said.
> Personally, I'd be in favor of a tag 11.0.3+6 for:
> http://hg.openjdk.java.net/jdk-updates/jdk11u/rev/a68aa56930c0
> 
> Thanks,
> Severin
> 
> [*] http://mail.openjdk.java.net/pipermail/jdk-updates-dev/2019-
> April/000859.html
> 
> > > I suggest that, in future, we aim to tag the release on the day of the
> > > deadline or the last working day before to avoid such confusion.
> >
> > I suggest, once again, that we mechanically lock the repository when we
> don't accept the pushes. Let
> > only the maintainers to push. Then Andrew can push the CPU update
> himself before unfreezing the repo.
> >
> > > [0] https://hg.openjdk.java.net/jdk-updates/jdk11u/rev/dd4470fa81fe
> > > [1] https://hg.openjdk.java.net/jdk-updates/jdk11u/rev/a68aa56930c0
> > > [2] https://hg.openjdk.java.net/jdk-updates/jdk11u/rev/22cfec306339
> >
> >