Do we create Jira Backport "bugs" for Skara /backport jdk17u-dev issues?
Lindenmaier, Goetz
goetz.lindenmaier at sap.com
Wed Jan 12 15:29:04 UTC 2022
Yes, you only need to create a backport bug by hand if you
want to backport a CSR. And only if you want to create a CSR.
> 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".
The normal proceeding is to first make the CSR, and only if
the CSR is done (and the pr is available, tested and reviewed)
add the jdk17u-fix-request label.
Adding that label is the last to do, because then it starts
to pop up in my filter
Please just delete the label form the Backport issue.
It was good to check whether these changes are fit for
17u before doing all the work!
Best regards,
Goetz.
> -----Original Message-----
> From: jdk-updates-dev <jdk-updates-dev-retn at openjdk.java.net> On
> Behalf Of Andrew Leonard
> Sent: Wednesday, January 12, 2022 4:00 PM
> To: jdk-updates-dev at openjdk.java.net
> Subject: Do we create Jira Backport "bugs" for Skara /backport jdk17u-dev
> issues?
>
> 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
More information about the jdk-updates-dev
mailing list