JDK 9 Release-Candidate Phase
The specific goals of this phase are to:
-
Fix all P1 bugs that are new in JDK 9 and critical to the success of this release;
-
Decommit from fixing any P1 bugs that are not new in JDK 9 and are not critical to this release, but were previously targeted to this release; and
-
Explicitly defer any P1 bugs that are new in JDK 9 but are either not critical to this release or cannot, for good reason, be fixed in this release.
All P2-P5 bugs must be left to future releases, regardless of
whether they are in product code, tests, or documentation. Fixes
with the noreg-doc or noreg-test labels,
in particular, now require explicit approval and must be P1.
There is no need to defer unfixed P2-P5 bugs explicitly.
From this point forward we will only promote a new build each week when there is a need to do so.
P1 bugs
The current list of candidate Release Candidate bugs can be found here: http://j.mp/jdk9-rc. If you're responsible for a bug on this list then you can take one of the following actions:
-
Develop a fix for the bug and then request approval to integrate it; or
-
If the bug is not new in JDK 9 (check the "Affects Version" field) then you can remove it from the list by clearing the "Fix Version" field, or by setting that field to
tbd_majorif the fix would only be suitable for a major release, or by setting that field totbd_minorif the fix would be suitable for any release, or by setting that field to a specific future release; or -
If the bug is new in JDK 9 but is not critical or cannot be fixed in time then you can request that the bug be deferred explicitly from the release via the bug deferral process that we adopted earlier for RDP 1.
In any case, do not change the priority of a bug in order to remove it from the list. The priority of a bug should reflect the importance of fixing it independent of any particular release, as has been standard practice for the JDK for many years.
P2-P5 bugs
The RC candidate list only contains P1 bugs. P2-P5 bugs are
irrelevant to the overall status of the release from this point
forward, regardless of whether or not they're targeted, so there's
no need to take any specific action on any P2-P5 bugs. You don't
need to defer them, either explicitly via the deferral process or
even implicitly by adjusting the "Fix Version" field, though you
can set the value of that field to tbd_major or
tbd_minor if you think that will be useful information
later on.
P2-P5 bugs whose fixes only affect tests (or test problem lists) or documentation or demos may no longer be fixed.
