Welcome to OpenJDK 8 Updates!
As a preamble, the project lead has established general guidelines for working on jdk8u.
OpenJDK 8 updates will be delivered on the same established quarterly cycle used by Oracle i.e. "the Tuesday closest to the 17th day of January, April, July and October."
Development takes place in the jdk8u-dev Mercurial repository 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 jdk8u 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 may want to continue reading here.
The contribution checklist is here. That page was written for OpenJDK 11 updates, but the same process is applicable for OpenJDK 8 updates as well.
New fixes should first be submitted to the development repository for the current version of OpenJDK, jdk/jdk, first. Most changes submitted to the OpenJDK 8 project will be backports from this repository. Occasional exceptions are made when an issue only applies to 8.
Everybody is encouraged to submit fixes for OpenJDK 8 updates by dropping a mail to the jdk8u-dev mailing list. Established community members will help new developers without commit access in getting their patch reviewed. Should you not be willing or not be able to drive a fix into OpenJDK 8 updates, you can still suggest changes. 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 8u tree, it should first be submitted for review.
Push approval for a fix is then requested by setting the jdk8u-fix-request label on the original JBS bug. The maintainer will either approve this by setting jdk8u-fix-yes or reject it by setting jdk8u-fix-no. Outstanding approvals can be monitored here. If, and only if, the fix is approved, it may be pushed to the appropriate jdk8u-dev repositories. Approved fixes show up in this JBS filter (login required).
During the later stages of a release cycle, the release enters rampdown. The master jdk8u repositories contain the latest version of that release, while the jdk8u-dev repositories are 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 jdk8u-critical-request label. 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 jdk8u-dev. The maintainers may approve with jdk8u-critical-yes, defer to jdk8u-dev or reject altogether. Outstanding approvals for critical fixes can be monitored here. If, and only if, the fix gets approved with jdk8u-critical-yes, it may be pushed to the jdk8u repository. Approved critical fixes show up in this JBS filter (login required).
At the end of the month prior to the release month, the jdk8u 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 jdk8u repository and source bundles made available.
- Tuesday, June 11th 2019: jdk8u-dev forest open (tag: jdk8u232-b00)
- Wednesday, July 24th 2019: First build promotion jdk8u-dev->jdk8u (tag: jdk8u232-b01)
- Wednesday, July 31st 2019: Second build promotion jdk8u-dev→jdk8u (tag: jdk8u232-b02)
- Wednesday, August 7th 2019: Third build promotion jdk8u-dev→jdk8u (tag: jdk8u232-b03)
- Wednesday, August 14th 2019: Fourth build promotion jdk8u-dev→jdk8u (tag: jdk8u232-b04)
- Wednesday, August 21st 2019: No build promotion due to lack of changes
- Wednesday, August 28th 2019: Final build promotion jdk8u-dev→ jdk8u (tag: jdk8u232-b05) & start of Rampdown phase
- Wednesday, September 4th 2019: No build promotion due to lack of changes during rampdown initiation
- Wednesday, September 11th 2019: First jdk8u build promotion (tag: jdk8u232-b06)
- Wednesday, September 18th 2019: Second jdk8u build promotion (tag: jdk8u232-b07)
- Wednesday, September 25th 2019: Last tag before code freeze (tag: jdk8u232-b08)
- Tuesday, October 15th 2019: GA; OpenJDK 8u232 released (tag: jdk8u232-ga, likely to be jdk8u232-b09)
OpenJDK 8u242 (preliminary)
- Thursday, September 5th 2019: jdk8u-dev forest open (tag: jdk8u242-b00)
- Wednesday, November 27 2019: Rampdown; last merge from jdk8u-dev to jdk8u
- Wednesday, December 25 2019: Last tag before code freeze
- Tuesday, January 14 2020: GA; OpenJDK 8u242 released (tag: jdk8u242-ga)
- Thursday, November 28th 2019: jdk8u-dev forest open (tag: jdk8u252-b00)
- 8u222-b10 (GA), July16th 2019 [Release] [Tag] [Binaries] [Missing changes vs 8u222 of Oracle] (JBS Login required) [Additional changes vs 8u222 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.
Standard Fix Requests
Critical Fix Requests
Filters for Release 8u232
Filters for Release 8u242
The jdk8u-dev forest for ongoing development can be cloned using this command:
hg clone jdk8u-dev;sh get_source.sh
The corresponding master forest jdk8u can be cloned using this command: hg clone
Recent space activity