[aarch64-port-dev ] Pending AArch64 patches for 8u and 11u

[Patrick Zhang OS]

"jdk8u-aarch64-fix-request" looks nice to me, could I start to use it to ask for approval if no objection? 
I had a practical case for this, https://bugs.openjdk.java.net/browse/JDK-8215976, a backport request to aarch64-port/jdk8u-shenandoah/jdk, but no progress for days. https://mail.openjdk.java.net/pipermail/aarch64-port-dev/2019-March/007025.html  

There is "jdk8u-critical-request", do we need "jdk8u-aarch64-critical-request" similarly?

Regards
Patrick

-----Original Message-----
From: aarch64-port-dev <aarch64-port-dev-bounces at openjdk.java.net> On Behalf Of Andrew Haley
Sent: Tuesday, March 12, 2019 4:26 PM
To: Aleksey Shipilev <shade at redhat.com>; aarch64-port-dev at openjdk.java.net
Subject: Re: [aarch64-port-dev ] Pending AArch64 patches for 8u and 11u

On 3/11/19 3:09 PM, Aleksey Shipilev wrote:
> On 3/11/19 4:04 PM, Andrew Haley wrote:
>> I'm thinking about what to do about backport approvals. For 11u it's 
>> clear: add the label "jdk11u-fix-request" to the bug database entry. 
>> For 8u it's not so clear because AArch64 is not in the 8u mainline. 
>> We could just use the "jdk8u-fix-request" anyway, even so. Thoughts?
> 
> That would be confusing, because backport tracking (either in JIRA or 
> external) would look for the backports resolved in openjdk8u*, which 
> is jdk8u/*, not aarch64-port.

OK. that makes sense.

> We have the same problem in Shenandoah 11u and 8u, and we "just"
> backport stuff into development versions without requesting backports 
> via JDK Updates process. Because, in retrospect, these downstream 
> repositories are not related to JDK Updates project at all.

Well, I'd disagree with that: they are related in the same way that A is a child of B.

How about "jdk8u-aarch64-fix-request" etc. ?

--
Andrew Haley
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671