[aarch64-port-dev ] [AARCH64] Proposal for tracking features, enhancements, and bugs for JDK 13 release

[Derek White]

Hi folks,

This is a proposal to help us track the aarch64 work that we’d like to go into the next JDK release [1]. This can avoid duplicate effort, duplicate tracking, and duplicate worry. I’ve talked to several folks at Oracle to come up with a process to use JBS (JDK Bug System) [2] to track without getting in Oracle’s way.

-----------------------------------------------------------------------------------------------------------------------------------------------
GENERAL ISSUE TRACKING
We should have everything we want to work on in the aarch64 port entered into JBS as bugs, enhancements, tasks (e.g. “test this on aarch64”), etc.

All aarch64 issues should have <CPU set to “aarch64”>, and <label set to “openjdk”> (which tends to keep Oracle from taking responsibility for the issue).

PROPOSING ISSUE FOR JDK 13 RELEASE
To propose a bug, enhancement, or task for JDK 13, <set Fix Version to 13>. This could be an issue you’re working on, or just an issue that you consider important for the next release [3]. Setting the flag is not an iron-clad commitment at this point, but a flag that we should consider this for the next release.

JEPs need to be handled separately!
We can’t set the Fix Version for any JEP implementation that has not yet been targeted. We can use our existing JEP tracker in Google Docs to track aarch64 implementations of JEPs [4].

EVALUATE ISSUES FOR JDK 13 RELEASE
Find all of the proposed issues with the JBS filter “AARCH64 To Do for JDK 13” https://bugs.openjdk.java.net/issues/?filter=36689. You can subscribe to the filter to get updates. You can also use the query “fixVersion = 13 AND resolution = Unresolved AND cpu = aarch64”.

We can comment (pro or con) about issues for JDK 13 by email or as comments in the issue itself. The result of an email discussion should be added as a comment. We can also consider if the Jira “voting” feature would be helpful to this process.

Issues rejected/postponed from JDK 13 should have the <Fix Version set to “tbd”>.

REALITY CHECK PHASE
As we close in on Rampdown Phase One, we should start postponing issues that won’t realistically make it into the next release. The issue’s assignee (and potential reviewers) should have a voice in the determination. If an issue doesn’t not have an assignee at this point, it should be postponed.

If we forget this step we will start getting anxious emails from Oracle about all of our outstanding bugs for JDK 13 ��

FYI - LOOKING FOR TROUBLE
There are a number of unassigned aarch64 issues. See JBS filter “AARCH64 Unassigned” https://bugs.openjdk.java.net/issues/?filter=36720

-----------------------------------------------------------------------------------------------------------------------------------------------

So that was a lot of text for a simple idea – set “cpu” and “label” appropriately, and argue about toggling “Fix Version”.

Please comment if this seems worthwhile or not, or if you have other suggestions.


  *   Derek

NOTE:
Expect the normal Oracle bug triage process to occasionally step on our handling of aarch64 issues – there are a lot of individuals thrown into triage work and they may not all understand that we have primary responsibility for aarch64 issues.

[1] http://openjdk.java.net/projects/jdk/13/
[2] If you don’t have JBS access (https://bugs.openjdk.java.net) we’ll try to help get you access and/or can make JBS changes for you.
[3] I have been searching for x86 and ppc enhancements that should be ported to aarch64. I may or may not handle these issues, but I think it’s worthwhile tracking them. And some of them seem urgent enough to propose for JDK 13.
[4] “Shared AARCH64 JVM Port Status”, see “Aarch64 CR” column. https://docs.google.com/spreadsheets/d/1JT3lFsiju60JSU43DWN8NjuCjjNVhkp7TltajdJCOr8/edit?usp=sharing