Do we create Jira Backport "bugs" for Skara /backport jdk17u-dev issues?

[Jie Kang]

I don't think you need to create a backport bug for the ones without a
CSR, and can follow the doc you linked that mentions applying the
fix-request label to the original bug. There is also commenting on the
original bug with a Fix Request to describe the reason for the
backport.

This document has useful guidance:
http://openjdk.java.net/projects/jdk-updates/approval.html

The backport bug is created automatically by Roboduke (I don't recall
when). E.g. look at the history of the bug and it's backport bugs
linked below (in the history of the backport bugs, you'll find all
changes were made by Roboduke)

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


Regards,

On Wed, Jan 12, 2022 at 10:01 AM Andrew Leonard <anleonar at redhat.com> wrote:
>
> Hi,
> I'm getting confused, please can someone put me straight on the backport
> process?
> The doc https://wiki.openjdk.java.net/display/JDKUpdates/JDK+17u says add a
> jdk17u-fix-request to the "original" bug, but if you use original
> bug->Create backport it labels the Backport bug with the
> "jdk17u-fix-request".
> Also using Skara /backport jdk17u-dev tags the original bug with the PR and
> does not create a Backport bug. Do I only need to create a Backport bug if
> I am creating a CSR, or should I always create one?
>
> Thanks,
> Andrew
>


--
Jie Kang
Associate Manager : Java Monitoring Team, Adoptium Team
Toronto Internship Program Lead
Red Hat Canada
https://keybase.io/jkang
1F5B34F61EF92DB4DCDDF195F034C81F60D402AA