[aarch64-port-dev ] macOS/Aarch64 workflow

Anton Kozlov akozlov at azul.com
Wed Sep 30 17:34:01 UTC 2020


Hi all,

Since the JEP for macOS/AArch64[1] became Candidate, we can work on the port
under the OpenJDK roof. That is, sharing and discussing changes that eventually
will be integrated as parts of the JEP implementation.

I know there are multiple parties willing to contribute, and this is great! To
understand what should be done and what somebody has done, I have started
filling in JDK-8253795: Implementation of JEP 391: macOS/AArch64 Port[2]. I
propose to use subtasks to track changes that constitute the port, and use
related links for other changes, like fixes for bugs earlier unnoticed, related
enhancements,...  These lists are not complete yet.

So far, for me it does _not_ look like the implementation will span for a large
number of commits. But anyway we need a way to effectively collaborate on code.
The chosen way should also ensure that the involved party has signed the OCA.

We can use jdk-sandbox[3], which serves exactly this need (apparently it has
been moved to git[4] after openjdk/jdk as well). But you have to be a JDK
Project Committer to use the sandbox.

It looks like another option for non-Committers is to use draft Pull Requests
on GitHub to openjdk/jdk repo, which would be the same as using
cr.openjdk.java.net. Then others could pull changes from openjdk/jdk/pull/...,
after ensuring the Skara bot have verified the OCA status of the PR.

There are other options, like a project or a repo under an existing project.
Let's discuss them.

Thanks,
Anton

[1] https://openjdk.java.net/jeps/391
[2] https://bugs.openjdk.java.net/browse/JDK-8253795
[3] https://cr.openjdk.java.net/~chegar/docs/sandbox.html
[4] https://github.com/openjdk/jdk-sandbox

On 26.09.2020 00:23, mark.reinhold at oracle.com wrote:
> https://openjdk.java.net/jeps/391



More information about the aarch64-port-dev mailing list