[gnu.andrew at redhat.com: Re: Additional Labels for Backport Work]

[Andrew Hughes]

Bringing discussion back to the 8u list.

----- Forwarded message from Andrew Hughes <gnu.andrew at redhat.com> -----

Date: Fri, 4 Sep 2020 17:10:24 +0100
From: Andrew Hughes <gnu.andrew at redhat.com>
To: Jesper Wilhelmsson <jesper.wilhelmsson at oracle.com>
Subject: Re: Additional Labels for Backport Work
User-Agent: Mutt/1.10.1 (2018-07-13)

On 22:03 Thu 27 Aug     , Jesper Wilhelmsson wrote:
> > On 27 Aug 2020, at 21:58, Martin Balao <mbalao at redhat.com> wrote:
> > 
> > On 8/27/20 1:48 PM, Mario Torre wrote:
> >> After a brief discussion today, it occurred to me that we can create
> >> backport bugs manually and assign them directly, wouldn't this be a
> >> better approach to track who is working on a specific backport?
> > 
> > Yes, I thought about this idea some time ago and discussing with Andrew
> > (@gnu_andrew) he raised a valid concern: end-up with lots of backport
> > bug duplicates when those manually created are not automatically
> > resolved when pushing the fix -and new ones being created-. We would
> > need to know exactly how to manually create bugs that are then resolved
> > when pushing. But then we need to rely on everybody getting it right.
> > I've seen duplicates already when manually creating backport bugs for CSRs.
> 
> For an 8u backport set the fixVersion to 8-pool to have hg updater resolve the issue. This should be standard practice for all bugs/backports in update releases. Always set fixVersion to X-pool unless you know for sure what release you need it to go into and are requesting that the fix should be included in the release in the rampdown phase.
> 
> /Jesper
> 

Except it doesn't seem to work with OpenJDK 8u at present e.g.

https://bugs.openjdk.java.net/browse/JDK-8160768

JDK-8251269 should have been resolved, but JDK-8252535 was created
instead.

I've mailed ops about this. I think it may be because '8u' is still
the Oracle proprietary fork for 8, and openjdk8u is the open version.

With 11u, it's the other way around (11.0.7 and 11.0.7-oracle, for
example), so hopefully things work as expected there.

I went the label route instead because it's less prone to error,
easier to correct if errors do occur and intended to be transient
(applied when you start work and removed when finished). Also the main
bug ID is the one to refer to and use in changesets. I wouldn't like
to see the additional confusion of backport IDs being used in mailing
list posts and commits.

Thanks,
--
Andrew :)

Senior Free Java Software Engineer OpenJDK Package Owner Red Hat,
Inc. (http://www.redhat.com)

PGP Key: ed25519/0xCFDA0F9B35964222 (hkp://keys.gnupg.net)
Fingerprint = 5132 579D D154 0ED2 3E04  C5A0 CFDA 0F9B 3596 4222



----- End forwarded message -----

-- 
Andrew :)

Senior Free Java Software Engineer
OpenJDK Package Owner
Red Hat, Inc. (http://www.redhat.com)

PGP Key: ed25519/0xCFDA0F9B35964222 (hkp://keys.gnupg.net)
Fingerprint = 5132 579D D154 0ED2 3E04  C5A0 CFDA 0F9B 3596 4222