Bug metadata updates for 11u bugs
christoph.langer at sap.com
Fri Jul 2 09:02:42 UTC 2021
I've reported this to ops yesterday already and Kevin Rushforth responded that they'll have a look.
After all, I think no corrective action is necessary because all those bugs will be promoted to b01 as soon as we tag OpenJDK 11.0.13+1 anyway. It's just invalid for the moment...
> -----Original Message-----
> From: jdk-dev <jdk-dev-retn at openjdk.java.net> On Behalf Of Alan Bateman
> Sent: Freitag, 2. Juli 2021 10:25
> To: Aleksey Shipilev <shade at redhat.com>; jdk-dev at openjdk.java.net
> Subject: Re: Bug metadata updates for 11u bugs
> On 02/07/2021 08:56, Aleksey Shipilev wrote:
> > Hi,
> > I have a question about bug metadata handling. Consider this backport
> > history:
> > https://bugs.openjdk.java.net/browse/JDK-8268891
> > It was pushed to 11.0.13. Bots updated "Resolved In Build" to "team".
> > Then yesterday Saravana updated "Resolved In Build" to "b01". It does
> > seem the sibling backport to "11.0.13-oracle" got updated to "b01" at
> > the same time.
> > Does this reflect the tag in Oracle internal tree only? Or is it a bug
> > metadata update hiccup, i.e. the scripts updated both 11.0.13-oracle
> > (correctly) and 11.0.13 (unnecessarily)?
> This looks like a mistake rather than intentional, maybe a script doing
> bulk updates when an Oracle JDK build was promoted. Hopefully Saravana
> can fix it and the backport issues can be restored.
More information about the jdk-dev