[aarch64-port-dev ] Tracking aarch64 downstream backports

[Aleksey Shipilev]

On 4/25/19 2:02 PM, Andrew Haley wrote:
> On 4/25/19 12:09 PM, Aleksey Shipilev wrote:
>> We have the backports monitor [1] that tracks the status for the patches across the repositories.
>> For example, for AArch64-specific problems it currently prints this:
>>
>>> JDK-8219698: aarch64: SIGILL triggered when specifying unsupported hardware features
>>>
>>>   Original Bug:
>>>       URL: https://bugs.openjdk.java.net/browse/JDK-8219698
>>>       Reporter: Felix Yang
>>>       Assignee: Felix Yang
>>>       Priority: P4
>>>       Components: hotspot/runtime
>>>
>>>   Original Fix:
>>>         13: JDK-8219698, http://hg.openjdk.java.net/jdk/jdk/rev/72ce7dd54939, 57 day(s) ago
>>>
>>>   Backports and Forwardports:
>>>         12: 12.0.2, JDK-8220537, http://hg.openjdk.java.net/jdk-updates/jdk12u/rev/bc3f5be06d88, 44 day(s) ago
>>>         11: 11.0.4, JDK-8220535, http://hg.openjdk.java.net/jdk-updates/jdk11u-dev/rev/e0d47c058971, 44 day(s) ago
>>>          8: MISSING
>>>          7: Not affected
>>
>> Notice "8: MISSING" -- it says that while the issue has the "Affected Versions: 8", and there is no
>> corresponding backport in 8u. Which stands to reason, as aarch64-port is not in mainline 8u.
> 
> This bug is low priority, near-zero impact. If anyone wants to request
> an 8u backport I'll reply with jdk8u-fix-no, which will solve that
> problem.

Sure, you can do that. And then the report would say "REJECTED", and it would be out of the list.
Importantly, it would be explicitly rejected by maintainers, rather than being ambiguously in
"MISSING" limbo. What concerns me that we can have bugs that you want in aarch64-port, but don't
know it is missing (until you discover that, much to your surprise when dealing with
customer-reported bug :]). This is what backports monitor is for.

-Aleksey