[aarch64-port-dev ] Tracking aarch64 downstream backports

Aleksey Shipilev shade at redhat.com
Tue Apr 30 09:14:22 UTC 2019


On 4/30/19 10:00 AM, Andrew Haley wrote:
> On 4/29/19 2:06 PM, Andrew Haley wrote:
>> On 4/29/19 9:46 AM, Aleksey Shipilev wrote:
> Ops points out that there is already "11-shenandoah" and
> "8-shenandoah". Given that the only active tree in aarch64-port is
> http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/ we could use
> "8-shenandoah". The problem is that it's a bit confusing, but I can't
> see a way to help that.

8-shenandoah is:
  http://hg.openjdk.java.net/shenandoah/jdk8u/

While we can technically reuse that version tag for:
  https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/

...I think the important part here is "aarch64", not "shenandoah". So, maybe the version tag should
be "8-aarch64". And, given there is only a single active tree in aarch64, it would be unambiguous.
It would be awkward to mark AArch64-specific bugs with 8-shenandoah, when those issues are not
related to Shenandoah at all, but rather relate to 8u aarch64 port.

-Aleksey



More information about the aarch64-port-dev mailing list