Welcome to JDK 8 Updates!
As a preamble, the project lead has established general guidelines for working on jdk8u.
JDK 8 updates will be delivered in a quarterly cylecycle. Usually releases happen mid of January, April, July and October.
The jdk8u-dev mercurial repository is the default repository for collecting changes. The jdk8u repository is used for stabilizing and delivering the quarterly JDK 8 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 JDK8 JDK 8 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 8 updates.
Everybody should feel encouraged to suggest fixes for JDK 8 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. The page was written for JDK 11 updates, but holds for JDK8 JDK 8 updates as well.
Should you not be willing or not be able to drive a fix into OpenJDK 8 updates, you can still suggest changes by dropping a mail to the jdk8u-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 jdk8u-fix-request label on the original JBS bug. The maintainer will either approve by setting jdk8u-fix-yes or reject by setting jdk8u-fix-no. Outstanding approvals can be monitored here. If and only if the fix gets approved, it may be pushed to the jdk8u-dev repository forest. If a bug shows up in this JBS filter (login required) it is allowed for being pushed to jdk8u-dev.
When a JDK 8 update release is in ramp down (that is, it was brought to jdk8u already), push approval can still be requested using the jdk8u-critical-request label. However, the maintainers will only consider fixes that Oracle have brought to their correspondent JDK8 corresponding JDK 8 update release, fixes for high priority issues or important test fixes at this point. The maintainers may approve with jdk8u-critical-yes, defer to jdk8u-dev or reject. 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. If a bug shows up in this JBS filter (login required) it is allowed for being pushed to jdk8u.
- March 2019: jdk8u-dev forest open (tag: jdk8u222-b00)
- Tuesday, April 30 2019: Branch jdk8u-dev to jdk8u
- Wednesday, May 1 2019: First build (tag: jdk8u222-b01)
- Wednesday, May 29 2019: RDP2
- Wednesday June 26 2019: Last tag before code freeze
- Tuesday, July 16 2019: GA (tag: jdk8u222-ga)
- May 2019 jdk8u-dev forest open (tag: jdk8u232-b00)
- Tuesday, July 30 2019: Branch jdk8u-dev to jdk8u
- Wednesday, July 31 2019: First build (tag: jdk8u232-b01)
- Wednesday, August 28 2019: RDP2
- Wednesday, September 25 2019: Last tag before code freeze
- Tuesday, October 15 2019: GA (tag: jdk8u232-ga)
- August 2019 jdk8u-dev forest open (tag: jdk8u242-b00)
- GA April 2019 [tag] [Released] [Missing changes vs 8u212 of Oracle] (JBS Login required) [Additional changes vs 8u212 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 8u222
Filters for release 8u232
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