- Andrew Haley (Lead Maintainer)
JDK 11 updates will be delivered in a quarterly cyle. Usually releases happen mid of January, April, July and October.
Update fixes are collected in the The mercurial repository jdk11u-dev repository and update releases will be stabilized in the jdk11u repository. At the beginning of a release cycle, the jdk11u-dev repository will be tagged with jdk11.0.x+0, where x is a placeholder for the update release. At a certain point in time a release cycle enters ramp down phase 2 (RDP2) and jdk11u-dev will be transported to jdk11u. In jdk11u, stabilization is done by (only) accepting high priority or test fixes. jdk11u will be tagged on a weekly basis, when new changesets have been pushed. The tags will have the format of jdk11.0.x+n, where x is a placeholder for the update release and n is the monotonically increasing build number. At the release day, security changes that have been collected in a secure environment and tested internally at Red Hat will be merged into jdk11u and the final tags jdk11.0.x+n and jdk11.0.x-ga will be set. Each tag that gets set in jdk11u will be integrated back to jdk11u-dev in a timely manner.
is the standard repository for collecting changes. The jdk11u repository will be used for stabilizing and delivering the quarterly JDK 11 update releases.
Fixes in the OpenJDK should generally be done upstream in the development repository jdk/jdk. As a matter of fact, changes to JDK11 updates will mostly be backports of issues from upstream.
Everybody should feel encouraged to suggest updates for JDK 11 updates and do the work to get them in. Everybody can do it, at least for the most parts. For details, on how to do it, continue reading here.
Should you, for some reason, not be willing or able to drive a fix into OpenJDK 11 updates, you can still suggest changes by dropping a mail to jdk-updates-dev and asking. But by doing only that, you are at the grace of some community member to pick it up and do the work for you.
In general we follow the common rules for the jdk-updates project.
Push approval for a fix is requested by setting the jdk11u-fix-request label on the original bug. The maintainer will either approve by setting jdk11u-fix-yes or reject by setting jdk11u-fix-no. If and only if the fix gets approved, it may be pushed to the jdk11u-dev repository. It will then reach the next
When a a JDK 11 update release that is not yet in RDP2 phase.If a fix needs to be integrated into the current JDK 11 update release after RDP2, this can be requested via already in ramp down (jdk11u), a fix can be requested for consideration using the jdk11u-critical-request label. The maintainer will may approve with jdk11u-critical-yes, defer to jdk11u-dev or reject with jdk11u-critical-no. If and only the fix gets approved with jdk11u-critical-yes, it may be pushed to the jdk11u repository. Eligible candidates for approval after RDP2 would be fixes that Oracle has brought to their correspondent JDK11 update release, fixes for high priority issues and test fixes.
In the very last days before the release date, we won't accept any pushes to jdk11u in order to have the maintainers of the security fixes finish up their testingUse the filters to check push eligibility...