Welcome to

OpenJDK 8 Updates!

JDK OpenJDK 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 OpenJDK 8 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 jdk8u-dev mercurial 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.

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 may want to continue reading here.

Contributing

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 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.Most changes submitted to the OpenJDK 8 project will be backports from this repository. Occasional exceptions are made when an issue only applies to OpenJDK 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. For details on the process involved, continue reading here. This page was written for OpenJDK 11 updates, but the same process is applicable for OpenJDK 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 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.

Fix Approvals

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 gets is approved, it may be pushed to the appropriate jdk8u-dev repository forest. If a bug shows  repositories. Approved fixes show 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), .

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. However, the maintainers will only consider fixes that Oracle have brought to their corresponding JDK 8 update release, fixes for high priority issues or important test fixes at this pointAs 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. If a bug shows Approved critical fixes show up in this JBS filter (login required) it is allowed for being pushed to jdk8u.

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.

Repository Status

jdk8u-dev: Collecting Development of 8u222 fixes. Pushes after jdk8u-fix-yes approval. Check here for clearance.

jdk8u: Closed . Pushes after jdk8u-critical-yes approval. Check here for clearancefor anything other than regular weekly merges.

Timelines

OpenJDK 8u222

• March 2019: jdk8u-dev forest open (tag: jdk8u222-b00)
• TuesdayWednesday, May 28 29th 2019: RDP2, Rampdown; last merge from jdk8u-dev to jdk8u
• TuesdayWednesday, June 25 26th 2019: Last tag before code freeze
• Tuesday, July 16 17th 2019: GA; OpenJDK 8u222 released (tag: jdk8u222-ga)

OpenJDK 8u232

• WednesdayThursday, May 30th 2019: jdk8u-dev forest open (tag: jdk8u232-b00)
• TuesdayWednesday, August 27 28th 2019: RDP2, Rampdown; last merge from jdk8u-dev to jdk8u
• TuesdayWednesday, September 24 25th 2019: Last tag before code freeze
• Tuesday, October 15 15th 2019: GA; OpenJDK 8u232 released (tag: jdk8u232-ga)

OpenJDK 8u242

• WednesdayThursday, August 28 29th 2019: jdk8u-dev forest open (tag: jdk8u242-b00)

Releases

Latest: 8u212

• 8u212-b03 (GA April 2019 [tag), April 16th 2019 [Release] [Tag] [ReleasedBinaries] [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 filters will only work for users that are logged into JBS.

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]

Source code

The jdk8u-dev forest for ongoing development can be cloned using this command:  hg clone http://hg.openjdk.java.net/jdk8u/jdk8u-dev;cd jdk8u-dev;sh get_source.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