OpenJDK 11 Updates!
JDK OpenJDK 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.
JDK OpenJDK 11 updates will be delivered in a on the same established quarterly cycle. Usually releases happen mid used by Oracle i.e. "the Tuesday closest to the 17th day of January, April, July and October."
The Development takes place in the jdk11u-dev mercurial Mercurial repository is the default repository for collecting changes. The jdk11u repository is used for stabilizing and delivering the quarterly JDK 11 update releases. and should be the primary place for OpenJDK committers to submit their work.
Code from the development repository is regularly tagged and promoted to the master jdk11u repository, which is used to stabilize and deliver the quarterly releases. Distributors should use this as their primary source for creating OpenJDK builds.
For further process details you might want to continue reading here.
Fixes New fixes should first be submitted to the OpenJDK must generally be done in the upstream development repository for the current version of OpenJDK, jdk/jdk, first. As a matter of fact, changes to JDK 11 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 Most changes submitted to the OpenJDK 11 project will be backports from this repository. Occasional exceptions are made when an issue only applies to 11.
Everybody is encouraged to submit fixes for OpenJDK 11 by dropping a mail to the jdk-updates-dev mailing list. Established community members will help new developers without commit access in getting their patch reviewed. For details on the process involved, continue reading here.
Should you not be willing or not be able to drive a fix into JDK 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.
If the backport requires more than just cosmetic changes (file location changes, copyright header updates) to apply to the 11u repository, it should first be submitted for review.
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 Approved fixes show 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), .
During the later stages of a release cycle, the release enters rampdown. The master jdk11u repository contains the latest version of that release, while the jdk11u-dev repository is used to start work on the next release. If a change needs to be pushed to a release in rampdown, 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 corresponding JDK 11 update release, fixes for high priority issues or important test fixes at this point. As the name of this tag suggests, this process is intended for fixes such as major regressions that must make the release. More minor bugs and new features should go in the next release being developed in jdk11u-dev. The maintainers may approve with jdk11u-critical-yes, defer to jdk11u-dev or reject altogether. 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 Approved critical fixes show up in this JBS filter (login required) it is allowed for being pushed to jdk11u.
At the end of the month prior to the release month, the jdk11u repository is declared frozen so embargoed security fixes can be added in private during the final few weeks. On release day, the final version will be pushed to the jdk11u repository and source bundles made available.
- March 2019: jdk11u-dev repo open (tag: jdk-11.0.4+0)
- Tuesday, April 30 May 28 2019: Branch Rampdown; last merge from jdk11u-dev to jdk11u
- Wednesday, May 1 2019: First build (tag: jdk-11.0.4+1)
- Wednesday, May 29 2019: RDP2
- Wednesday June 26 Tuesday, June 25 2019: Last tag before code freeze
- Tuesday, July 16 2019: GA; OpenJDK 11.0.4 released (tag: jdk-11.0.4-ga)
- Wednesday, May 29: 2019 jdk11u-dev repo open (tag: 11.0.5+0)
- Tuesday, July 30 August 27 2019: Branch Rampdown; last merge from jdk11u-dev to jdk11u
- WednesdayTuesday, July 31 2019: First build September 24 2019: Last tag before code freeze
- Tuesday, October 15 2019: GA; OpenJDK 11.0.5 released (tag: jdk-11.0.5+1-ga)
OpenJDK 11.0.6 (preliminary)
- Wednesday, August 28 2019: RDP2Wednesday, September 25 2019: jdk11u-dev repo open (tag: 11.0.6+0)
- Tuesday, November 26 2019: Rampdown; last merge from jdk11u-dev to jdk11u
- Tuesday, December 24 2019: Last tag before code freeze
- Tuesday, October 15 2019January 14 2020: GA; OpenJDK 11.0.6 released (tag: jdk-11.0.56-ga)
- Wednesday, November 27 2019: jdk11u-dev repo open (tag: 11.0.67+0)
- 11.0.4+11 (GA), July 16th 2019, [Release] [Tag] [Binaries] [Missing changes vs 11.0.3-4 of Oracle] (JBS Login required) [Additional changes vs 11.0.3-4 of Oracle] (JBS Login required)
Older releases can be found in the archive.
Some filters will only work for users that are logged into JBS.