Additional Labels for Backport Work

[Jesper Wilhelmsson]

> On 27 Aug 2020, at 22:03, Jesper Wilhelmsson <jesper.wilhelmsson at oracle.com> 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

Btw. I'd be happy to include some documentation around this in the OpenJDK Developers' Guide once it's settled how to do things.
/Jesper