[8u-communication] JDK 8u202 RDP2

[Severin Gehwolf]

On Wed, 2018-11-21 at 16:05 +0000, Andrew Hughes wrote:
> On Wed, 21 Nov 2018 at 10:41, Severin Gehwolf <sgehwolf at redhat.com> wrote:
> > 
> > Hi Sean,
> > 
> > On Fri, 2018-10-26 at 13:35 +0100, Seán Coffey wrote:
> > > Thanks to all for the JDK 8u202 contributions to date. We'll enter RDP2
> > > on morning of 29th October (GMT). All changes in the jdk8u-dev forest
> > > will then be synced to the jdk8u master forest.
> > > 
> > > Once we pass the RDP2 milestone, jdk8u-dev will collect fixes for the
> > > next OpenJDK 8u release which will be led by others. I propose that an
> > > `openjdk8u` fix version be attributed to such fixes in JBS. A similar
> > > value was used for the OpenJDK 7u Project when maintainer duties were
> > > handed over to Red Hat. Only critical fixes will be accepted into 8u202
> > > post RDP2. The process for such requests is described on the Project
> > > page[1].
> > 
> > Any details as to when the RDP milestone will be done and fixes can be
> > collected for a post-u202 release? Do I need to label pending fixes
> > with 'openjdk8u' in JBS? If I do so, what needs to happen next for
> > fixes to get in?
> > 
> > My concern is that fixes will be lost in traffic in the time between
> > now and January 2019.
> > 
> > Thanks,
> > Severin
> > 
> > > regards,
> > > Sean.
> > > 
> > > [1] http://openjdk.java.net/projects/jdk8u/phase2/phase2-process.html
> > > 
> 
> That's already happening if you look at:
> 
> https://bugs.openjdk.java.net/browse/JDK-8029661
> 
> The 8u backport went into 'openjdk8u'.

Heh, I've pushed that patch for Martin :)

Perhaps it's because it's been the only one which happens to have been
pushed after u202 has been forked Oracle internally? After that I
haven't seen many approvals for jdk8u, perhaps because current
maintainers are reluctant to approve something they won't maintain any
more when the release happens? It's a bit of a mystery to me.

Thanks,
Severin