- Loading...
| CSS Stylesheet |
|---|
.wiki-content .confluenceTh,
.wiki-content .confluenceTd {
border: 2px solid #e76f00;
} |
| After a new Project Lead was not identified and several months of inactivity, the Project was dissolved Apr 2023. Discussion about reinstating a JDK 7 Updates Project may be held on discuss. |
...
No.
The final draft of the OpenJDK Community Bylaws defines a JDK Release Projects as "New releases of Java SE Platform implementations".
...
The dichotomy between OpenJDK 6 and the 6 update train allowed for some experimentation with very lightweight release management processes. Since this Project will serve as the basis for Oracle JDK 7 Update releases, it will likely need to develop more formal release processes then OpenJDK 6 did for code review, putback approval, repository management and bug management, the details of which are TBD on the Project mailing list.
...
Yes.
As with OpenJDK 6, security fixes are first kept confidential and applied to a private forest before being pushed to the public forest as part of the general synchronized publication of the fix to affected JDK release trains. In addition, they will not go through the public code review and putback approval process, and their corresponding issues in the Project's issue tracker will not be publicly visible.
The schedule for Oracle Java SE Critical Patch Updates is publicly available.
Security fixes for this Project's source code will be made available in the JDK 7 Update Project around the same time as they're released in products from Oracle.
...
See the phase 2 process page.
...
For processes regarding JDK 8, please see the JDK 8 Project page.
In general, the JDK 8 9 Project is the right place to discuss new features.
...