Welcome to JDK 8 Updates!

JDK 8 updates are a separate project of the OpenJDK. Andrew Haley serves as the Project Lead. The list of Reviewers, Committers, and Authors can be found in the jdk8u entry of the OpenJDK Census.

Anchor
maintainers maintainers

Maintainers

• Andrew Haley
• Andrew Hughes

General information

As a preamble, the project lead has established general guidelines for working on jdk8u.

JDK 8 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 jdk8u-dev repository forest and update releases will be stabilized in the jdk8u repository forest. At the beginning of a release cycle, the jdk8u-dev repository forest will be tagged with jdk8u<x>-b00, where x is a placeholder for the update release (e.g. 212). At a certain point in time a release cycle enters ramp down phase 2 (RDP2) and jdk8u-dev will be transported to jdk8u. In jdk8u, stabilization is done by (only) accepting high priority or test fixes. jdk8u will be tagged on a weekly basis, when new changesets have been pushed. The tags will have the format of jdk8u<x>-b<nn>, where x is a placeholder for the update release and nn is the monotonically increasing double digit 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 jdk8u and the final tags  jdk8u<x>-b<nn> and  jdk8u<x>-ga will be set. Each tag that gets set in jdk8u will be integrated back to jdk8u-dev in a timely manner.

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.

Contributing

Fixes to the OpenJDK must generally be done in the upstream development repository jdk/jdk first. As a matter of fact, changes to JDK8 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 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.

Fix Approvals

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. It will then reach the next JDK 8 update release that is not yet in RDP2 phase.If a fix needs to be integrated into the current JDK 8 update release after RDP2, this can be requested via 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. The maintainer will However, the maintainers will only consider fixes that Oracle have brought to their correspondent JDK8 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 with jdk8u-critical-no. 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 forest. Eligible candidates for approval after RDP2 would be fixes that Oracle has brought to their correspondent JDK8 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 jdk8u in order to have the maintainers of the security fixes finish up their testing repository. If a bug shows up in this JBS filter (login required) it is allowed for being pushed to jdk8u.

Status

jdk8u-dev: Waiting for hgupdater changes to start collecting Collecting 8u222 fixes. Pushes after jdk8u-fix-yes approval. Check here for clearance.

jdk8u: Collecting 8u212 fixesClosed. Pushes after jdk8u-critical-yes approval.

Fix Requests

Standard

[Unapproved requests] [All Requests] [All approved requests] [Approved requests without push]

Critical

[Unapproved critical requests] [All critical requests] [All approved critical requests] [Approved critical requests without push]

Timelines

JDK 8u212 timeline

• Mid March 2019 RDP2
• Early April 2019 RC phase (code freeze)
• Mid April 2019 GA

Check here for clearance.

Timelines

OpenJDK 8u222JDK 8u222 timeline

• 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)

JDK OpenJDK 8u232 timeline

• May 2019 jdk8u-dev forest open (tag: jdk8u232-b00)
• Late August 2019 RDP2
• Early October 2019 RC phase (code freeze)
• Mid October 2019 GA

Advanced JBS filters

• )
• 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)

OpenJDK 8u242

• August 2019 jdk8u-dev forest open (tag: jdk8u242-b00)

Releases

Latest: 8u212

• 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.

JBS filters

Some The filters will only work for users that are logged into JBS.

8u212:

Open Downports Oracle -> OpenJDK: https://bugs.openjdk.java.net/issues/?filter=36394

Additional commits in OpenJDK vs. Oracle: https://bugs.openjdk.java.net/issues/?filter=36458

8u222:

Open Downports Oracle -> OpenJDK: https://bugs.openjdk.java.net/issues/?filter=36456

Additional commits in OpenJDK vs Oracle: https://bugs.openjdk.java.net/issues/?filter=36459

8u232:

Open Downports Oracle -> OpenJDK: https://bugs.openjdk.java.net/issues/?filter=36513

Standard fix requests

[All Requests] [Approved requests] [Approved requests without push] [Unapproved requests]

Critical fix requests

[Critical requests] [Approved critical requests] [Approved critical requests without push] [Unapproved critical requests]

Filters for release 8u222

[Open Downports Oracle -> OpenJDK] [Additional commits in OpenJDK vs Oracle]

Filters for release 8u232

[Open Downports Oracle -> OpenJDK] [Additional commits in OpenJDK vs Oracle]Additional commits in OpenJDK vs Oracle: https://bugs.openjdk.java.net/issues/?filter=36512

Source code

The jdk8u-dev forest for ongoing development can be cloned using this command:  hg  hg clone http://hg.openjdk.java.net/jdk8u/jdk8u-dev;cd jdk8u-dev;sh get_source.sh sh 

The corresponding master forest jdk8u can be cloned using this command: hg clone http://hg.openjdk.java.net/jdk8u/jdk8u;cd jdk8u;sh get_source.sh In addition, the source code for the last release, 8u202, is available by cloning the 8u master forest : http://hg.openjdk.java.net/jdk8u/jdk8u and using the 'jdk8u202-ga' mercurial tag.sh