[aarch64-port-dev ] Tracking aarch64 downstream backports
Aleksey Shipilev
shade at redhat.com
Mon Apr 29 08:46:44 UTC 2019
On 4/26/19 4:44 PM, Andrew Haley wrote:
> On 4/25/19 1:16 PM, Aleksey Shipilev wrote:
>>> 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.
>
> OK, got that. Thanks.
So... Would you request the new version from ops@, or we just wait for whatever future brings with
repository consolidation some (unknown) time later? Either way is fine with me, just want to
understand if I should scratch this off my todo list.
-Aleksey
More information about the aarch64-port-dev
mailing list