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

Andrew Leonard anleonar at redhat.com
Wed Jan 12 16:48:19 UTC 2022


So I hunted for any existing other jdk-updates PRs labelled with "csr" and
could not find any, but I did find one via Jira but it wasn't labelled with
"csr" : https://github.com/openjdk/jdk17u/pull/110
So I am guessing the Skara csr process does not work with jdk-updates ?

On Wed, Jan 12, 2022 at 4:25 PM Andrew Leonard <anleonar at redhat.com> wrote:

> But it's got the correct CSR now :-)
>
>
> On Wed, Jan 12, 2022 at 4:25 PM Andrew Leonard <anleonar at redhat.com>
> wrote:
>
>> Tried changing PR comment issue, but now I get:
>> !  Issue of type Backport is not allowed for integrations
>>
>> Puzzled?
>>
>> On Wed, Jan 12, 2022 at 4:07 PM Andrew Leonard <anleonar at redhat.com>
>> wrote:
>>
>>> So i'm trying to correct my /backport created PR so it points at the
>>> correct jdk-17.0.3 CSR, but the "bot" keeps changing it back again!
>>> Here's the PR: https://github.com/openjdk/jdk17u-dev/pull/82
>>> Each time I change it  to point at the jdk-17.0.3 CSR (JDK-8279926), it
>>> changes the CSR reference to point back at the already approved jdk(tip)
>>> CSR (JDK-8277755).
>>>
>>> Would I be right in guessing I need to change the PR title to the name
>>> of the Backport bug? (JDK-8279925)
>>>
>>> Thanks
>>> Andrew
>>>
>>>
>>> On Wed, Jan 12, 2022 at 3:29 PM Lindenmaier, Goetz <
>>> goetz.lindenmaier at sap.com> wrote:
>>>
>>>> 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