JDK 9 Feature-Complete Extension Request Process
Requesting an extension
If you own a JEP or a small enhancement that is not yet complete
then you can request an FC extension as follows: Update the JBS
issue to add a comment whose first line is "FC Extension Request".
In that comment describe the remaining work to be done, the risk
level, a brief justification, and your best estimate of the date by
which the feature will be complete. Add the label
jdk9-fc-request to the issue.
If you own a JEP that's targeted to JDK 9, but won't make it, then please propose to drop it; this will move the JEP back to the Candidate state unless there are strong objections.
If you own a small enhancement whose fix version is 9, but won't make it, then please clear the fix-version field.
Reviewing extension requests
The Area Leads, relevant Group and Project Leads, and the JDK 9 Project Lead will review pending extension requests on a regular basis, at least weekly if not more often. One of us will take one of the following actions:
Approve the request by adding the label
Reject the request by adding the label
jdk9-fc-no, along with a comment describing the reason for this action.
Request more information by adding the label
nmi" = "needs more information"), along with a comment describing what information is requested.
In any case, do not remove the
JBS query for pending requests:
Responding to actions taken on your request
If you're asked to provide more information for an FC extension request then please do so in a new comment in the issue, and then remove the
jdk9-fc-nmilabel so that we see that it's ready for re-review.
If your request is approved then update the issue's due date to the expected completion date.
Notes on JEPs
If a JEP has been granted an FC extension then enhancement issues that block the JEP's issue are automatically considered to have FC extensions.
If a JEP has not yet been targeted to JDK 9 then you can still propose to target it to the release, but going forward the bar for accepting new features will be increasingly high.
Area, Group, & Project Leads
The Area Leads are Mikael Vidstedt (VM) and Brian Goetz (Language & Libraries). The relevant Group Leads are as follows, per the Census:
Sergey Bylokhov AWT Tim Bell Build Jonathan Gibbons Compiler Alan Bateman Core Libraries Vladimir Kozlov HotSpot Masayoshi Okutsu Internationalization Michael McMahon Networking Kevin Rushforth OpenJFX Dalibor Topic Porters Sean Mullan Security Staffan Larsen Serviceability Alexander Scherbatiy Swing Phil Race 2D Graphics & Sound