[aarch64-port-dev ] macOS/Aarch64 workflow

[Anton Kozlov]

On 01.10.2020 11:51, Andrew Haley wrote:
> It is more conventional, and IMO it would make more sense, to use a branch
> in the aarch64-port repo. Ops at openjdk is working on it.

I have looked through my mailbox, I hope you mean an aarch64 git repo (and not
the hg one[1]). But I'm not sure this was discussed before in public.

I see no benefit of an aarch64 branch, now you have to be an aarch64 project
committer to push there. More, there are downsides. In jdk-sandbox, you can
have multiple branches for the same purpose. I'm aware of at least three
implementations that do share a lot of in common. It will be very useful to see
them side-by-side and pick good and bad parts in each. Second, it will be
possible to commit something wrong and then fix the history (if we screwed up
and it prevents reviewing -- the point of having a pile of fixes in public). We
can also relax a bit, and avoid creating a Jira bug for each commit.

Sometime later, we may need a repo carved in stone, but at such an early phase,
I don't see a real value here.

To demonstrate, we have started publishing our changes in a sandbox branch [2].
It is possible to e.g. split a commit in two: to copy linux_aarch64[3] and to
adapt that to bsd platform[4]. I hope the latter will be much easier to review.
(I'll promise we'll avoid rebasing etc. in that branch, unless totally
necessary and will communicate prior doing that; but we may create another
version of that branch with the same content but "pretty" history)

I hope other implementations will show up soon, so we will be able to do 
a peer-review. And please welcome to look at the branch at the sandbox.

Thanks,
Anton

[1] https://hg.openjdk.java.net/aarch64-port/
[2] https://github.com/openjdk/jdk-sandbox/commits/JEP-391-branch
[3] https://github.com/openjdk/jdk-sandbox/commit/f9cdb3ffb5123ebbcd7a5ab3eee3db374b165f2f
[4] https://github.com/openjdk/jdk-sandbox/commit/58a63b60cbeffe91ebebe0b6db764368c1b1e210