[aarch64-port-dev ] Tracking aarch64 downstream backports

Aleksey Shipilev shade at redhat.com
Thu Apr 25 12:08:59 UTC 2019


On 4/25/19 2:02 PM, Andrew Haley wrote:
>> We can do the same for AArch64-port. To do this, we need Project
>> Lead to ask ops@ for a special version tag (e.g. "8-aarch64" or
>> something) in JIRA, and then we put this new version tag instead of
>> plain "8" on issues that affect only the downstream aarch64-8u
>> code. (Then I'll do some adjustments to backport monitor to handle
>> that new thing).
> 
> Either that or proceed apace with getting Shenandoah and AArch64
> merged.

"A bird in the hand is worth two in the bush" :)

Having a separate version label is 15 minutes setup deal, while merging Shenandoah 8u (development)
and AArch64-Shenandoah 8u (integration) forests is something that requires much, much more
discussion, work, and workflow changes. I'd prefer to have the list of missing backports in
aarch64-shenandoah earlier rather than much later. Your call if you would rather wait for repository
reshuffles.

-Aleksey



More information about the aarch64-port-dev mailing list