[aarch64-port-dev ] RFR: Bulk integration shenandoah/jdk8u -> aarch64-port/jdk8u-shenandoah 2018-09-17

[Aleksey Shipilev]

On 09/19/2018 06:55 PM, Andrew Hughes wrote:
> The changes look ok to me too. Is there a reason to maintain both shenandoah/jdk8u and
> aarch64-port/shenandoah-jdk8u, now that Shenandoah development has moved to an OpenJDK 12 base?

We treat shenandoah/jdk8u as "let's push backports there and see what happens" repository: we build
and test nightlies there, and sometimes our adopters find obvious bugs there that we don't want to
expose to anybody else, and/or there are adopter-requested features/fixes that might degrade
something else.

Integration repository like aarch64-port/shenandoah-jdk8u has the stuff we know works fine. It is
then open for larger testing and packaging. I think it makes more sense for 8u, because the GC
interface is rather intrusive in 8u, and there is elevated risk for breakages for non-Shenandoah
code. So, having the additional gateway where 8u integrations are reviewed is a plus. In 11+, almost
all of Shenandoah code is isolated, and has much less risk to regress anything else.

In other words, shenandoah/jdk8u is like jdk8u/dev, and aarch64-port/shenandoah-jdk8u is like
jdk8u/jdk8u :) What we need to do for this to work better is to get shenandoah/jdk8u ->
aarch64-port/shenandoah-jdk8u on a more frequent basis, so reviews stay trivial, and so that
whatever problems found in RPMs are fixed quickly.

Thanks,
-Aleksey