Backport proposal of the Marlin renderer in OpenJDK8

[Andrew John Hughes]

On 12/09/2019 20:54, Laurent Bourgès wrote:
> Hi Andrew B (& other Andrew in this thread),
> 
> I have an idea that could satisfy both approaches:
> - As the azul team backported already jdk9+ patches into their openjdk8 /
> zulu repository, it implies jdk8u patches are ready for integration and I
> already reviewed the code: zulu could be considered as both an incubator
> that proved Marlin works on jdk8 in production (as I did on my github).
> 
> Two solutions:
> - extract & apply all zulu-ready patches in order in jdk8u-dev
> - extract one big patch (from zulu) and apply it on jdk8u-dev
> I do not see any reason to use another incubator repository...
> 
> I can review all individual patches or the all-in-one and we are all done,
> up to the last patch backported in zulu 8 (version 0.9.1.1 merged in dec
> 2018 according to me).
> 
> Moreover I already maintain a github branch for the Marlin / openjdk (8):
> https://github.com/bourgesl/marlin-renderer/tree/openjdk?files=1
> It is my reference to easily compare with any jdk8 codebase.
> 
> From this first step, I will manage the missing patches to be up-to-date
> with latest jdk14 (v0.9.1.3 ie 2 patches) and future ones.
> 
> What do you think ?
> This approach requires some work from zulu team to publish jdk8 patches
> that I will review and I need a jdk8u sponsor to endorse, follow & push the
> patch train or the all-in-one patch integration.
> 
> Cheers,
> Laurent
> 

Is this Zulu public? Does it use OpenJDK bug IDs for the changesets?

As I said before, my preferred method is the backport of changesets
corresponding to individual OpenJDK bug IDs, so we have a clear idea of
what issues are now fixed in 8u.

Thanks,
-- 
Andrew :)

Senior Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)

PGP Key: ed25519/0xCFDA0F9B35964222 (hkp://keys.gnupg.net)
Fingerprint = 5132 579D D154 0ED2 3E04  C5A0 CFDA 0F9B 3596 4222
https://keybase.io/gnu_andrew