JDK 10 Rampdown Phase One
The overall goal of this phase is to ensure that we're fixing the bugs that need to be fixed, and that we understand why we're not fixing some bugs that perhaps ought to be fixed.
The specific goals are to:
-
Fix all P1–P3 bugs that are new in JDK 10,
-
Fix additional P1–P3 bugs targeted to JDK 10 as time permits, and
-
Explicitly defer any P1–P2 bugs that are new in JDK 10 but will not, for good reason, be fixed in JDK 10.
P4–P5 bugs must, at this point, be left to future releases unless they only affect tests or documentation, in which case they should be identified as such with the noreg-self or noreg-doc labels, respectively.
The current list of candidate Rampdown Phase One (RDP 1) bugs can be found here: http://j.mp/jdk-rdp-1. If you're responsible for a bug on this list then you can take one of the following actions:
-
Fix the bug (preferred), or
-
If the bug is not new in JDK 10 (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_feature
if the fix would only be suitable for a feature release, or by setting that field totbd_update
if the fix would be suitable for any release; or -
If the bug is new in JDK 10, and is P1 or P2, but it cannot be fixed in time or is too risky to fix, then you can request that the bug be deferred from the release via the bug deferral process.
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.
Enhancements
The overall feature set is, at this point, frozen. No further JEPs will be targeted to this release.
Late, low-risk enhancements that add small bits of missing functionality or improve usability are permitted with approval, especially when justified by developer feedback, but the bar is very high. API or other specification changes made by a JSR Expert Group are critical by definition, and will be approved. You can request approval for an enhancement via the late-enhancement request process.
Enhancements to tests and documentation do not require approval, as long as they are identified with appropriate noreg-self or noreg-doc labels.