- Loading...
The two main reasons for a new, separate JDK 8 Update Project are
No.
The final draft of the OpenJDK Community Bylaws defines a JDK Release Projects as "New releases of Java SE Platform implementations".
Update releases are not "new releases".
Yes.
As with OpenJDK 7u, 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 8 Update Project around the same time as they're released in products from Oracle.
All fixes require the approval of the release manager and may require additional technical review and approval at the discretion of the release manager. The Project's moderator can appoint a release manager for one or more repositories. Fixes must go into JDK Project first, unless they are JDK 8 Update specific, and be accompanied by an issue in the bug database.
See the phase 2 process page.
For now we'll use the Java bug database. We'll eventually migrate to the new OpenJDK bug system once that's available.
If you need an issue created in order to be able to commit into a repository, let the Project's moderator know on the Project's mailing list.
For processes regarding JDK Project , please see the Project page.
In general, the JDK Project is the right place to discuss new features.
...