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:

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:

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.


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.

Last update: 2017/12/24 04:47 UTC