Bug metadata updates for 11u bugs

[Praveen Mohan]

Hi All,



We have inadvertently updated all the 11.0.13 records while updating 11.0.13-oracle backports for 'Resolved in Build'.

We have reverted the change on all such records to what was there prior to our update.

Thanks to Severin for reverting some of them already. We will fix our scripts appropriately.



Sorry for the inconvenience.



Thanks,

Praveen



> -----Original Message-----

> From: jdk-dev <jdk-dev-retn at openjdk.java.net<https://mail.openjdk.java.net/mailman/listinfo/jdk-dev>> On Behalf Of Alan Bateman

> Sent: Freitag, 2. Juli 2021 10:25

> To: Aleksey Shipilev <shade at redhat.com<https://mail.openjdk.java.net/mailman/listinfo/jdk-dev>>; jdk-dev at openjdk.java.net<https://mail.openjdk.java.net/mailman/listinfo/jdk-dev>

> 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.

>

> -Alan