Welcome to JDK 11 Updates!
JDK 11 updates are part of the JDK updates project of the OpenJDK. Rob McKenna serves as the Project Lead. The list of Reviewers, Committers, and Authors can be found in the jdk updates section of the OpenJDK Census.
- Andrew Haley (Lead Maintainer)
JDK 11 updates will be delivered in a quarterly cyle. Usually releases happen mid of January, April, July and October.
The jdk11u-dev mercurial repository is the default repository for collecting changes. The jdk11u repository is used for stabilizing and delivering the quarterly JDK 11 update releases. For further process details you might want to continue reading here.
Fixes to the OpenJDK must generally be done in the upstream development repository jdk/jdk first. As a matter of fact, changes to JDK11 updates will mostly be backports of issues from upstream. There are exceptions when there's the need for a fix that only applies to JDK 11 updates.
Everybody should feel encouraged to suggest fixes for JDK 11 updates and do the work to get them in. Everybody can do it, at least the most parts of the work. For details on how to do it continue reading here.
Should you not be willing or not be able to drive a fix into OpenJDK 11 updates, you can still suggest changes by dropping a mail to the jdk-updates-dev mailing list. But by only doing that, you are at the grace of the community to pick up your suggestion.
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 JBS bug. The maintainers will either approve by setting jdk11u-fix-yes or reject by setting jdk11u-fix-no. Outstanding approvals can be monitored here. If and only if the fix gets approved, it may be pushed to the jdk11u-dev repository. If a bug shows up in this JBS filter (login required) it is allowed for being pushed to jdk11u-dev.
When a JDK 11 update release is in ramp down (that is, it was brought to jdk11u already), push approval can still be requested using the jdk11u-critical-request label. However, the maintainers will only consider fixes that Oracle have brought to their correspondent JDK11 update release, fixes for high priority issues or important test fixes at this point. The maintainers may approve with jdk11u-critical-yes, defer to jdk11u-dev or reject. Outstanding approvals for critical fixes can be monitored here. If and only if the fix gets approved with jdk11u-critical-yes, it may be pushed to the jdk11u repository. If a bug shows up in this JBS filter (login required) it is allowed for being pushed to jdk11u.
- March 2019: jdk11u-dev repo open (tag: jdk-11.0.4+0)
- Tuesday, April 30 2019: Branch jdk11u-dev to jdk11u
- Wednesday, May 1 2019: First build (tag: jdk-11.0.4+1)
- Wednesday, May 29 2019: RDP2
- Wednesday June 26 2019: Last tag before code freeze
- Tuesday, July 16 2019: GA (tag: jdk-11.0.4-ga)
- May 2019 jdk11u-dev repo open (tag: 11.0.5+0)
- Tuesday, July 30 2019: Branch jdk11u-dev to jdk11u
- Wednesday, July 31 2019: First build (tag: jdk-11.0.5+1)
- Wednesday, August 28 2019: RDP2
- Wednesday, September 25 2019: Last tag before code freeze
- Tuesday, October 15 2019: GA (tag: jdk-11.0.5-ga)
- August 2019 jdk11u-dev repo open (tag: 11.0.6+0)
- GA April 2019 [tag] [Released] [Missing changes vs 11.0.3-Oracle] (JBS Login required) [Additional changes vs 11.0.3-Oracle] (JBS Login required)
Older releases can be found in the archive.
Some filters will only work for users that are logged into JBS.