Versions Compared

Old Version 9

changes.mady.by.user Christoph Langer

Saved on

compared with

New Version Current

changes.mady.by.user Andrew Hughes

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Update schedule and freeze for 11.0.29 release

Welcome to

...

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 of section of the OpenJDK Census.

Anchor
maintainers
maintainers
Maintainers

Processes and Infrastructure

Retired Maintainers

Releases

Latest GA release: 11.0.28+6 (GA), July 15th 2025, [Release] [Tag] [Binaries]

Older releases can be found in the archive.

General Information

OpenJDK JDK 11 updates will be delivered in a quarterly cyle. Usually releases happen mid on the same established quarterly cycle used by Oracle i.e. "the third Tuesday of January, April, July and October."

Development takes place Update fixes are collected in the jdk11u-dev Git repository and update releases will be stabilized in the jdk11u repository. At the beginning of a release cycle, the jdk11u-dev repository will be tagged with jdk11.0.x+0, where x is a placeholder for the update release. At a certain point in time a release cycle enters ramp down phase 2 (RDP2) and jdk11u-dev will be transported to jdk11u. In jdk11u, stabilization is done by (only) accepting high priority or test fixes. jdk11u will be tagged on a weekly basis, when new changesets have been pushed. The tags will have the format of jdk11.0.x+n, where x is a placeholder for the update release and n is the monotonically increasing build number. At the release day, security changes that have been collected in a closed infrastructure by RedHat will be merged into jdk11u and the final tags jdk11.0.x+n and jdk11.0.x-ga will be set. Each tag that gets set in jdk11u will be integrated back to jdk11u-dev in a timely manner.

...

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.

Contributing

New fixes should first be submitted to the development repository for the current version of OpenJDK, jdk/jdk or higher updates repositories. Most changes submitted to the OpenJDK 11 project will be backports from these. Exceptions are made if an issue only applies to 11.

Everybody is encouraged to submit fixes for OpenJDK 11 by creating a pull request to the jdk11u-dev Git repository. Established community members will help new developers without commit access in getting their patch reviewed. For details on the process involved, continue reading these backport instructions.

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.

Fix Approvals

In general we follow the common rules for the jdk-updates project. Please note that these common rules do not allow enhancements to be back-ported, only fixes to bugs.

In addition this list, we will consider

  • Build system improvements, particularly for stability and reproducibility
  • Changes necessary to make 11u work on new operating systems and hardware

However, if there is an enhancement that provides substantial benefit to OpenJDK 11u users and it is of low risk, we will consider it. Please ask on the jdk-updates mailing list mailing list if you are in any doubt about whether your proposed backport might qualify.

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. Approved fixes show up in this JBS filter (login required).

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. 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 that get approved (via the jdk11u-fix-yes label) have to be pushed to the jdk11u-dev repository. Those changes will then reach the next JDK 11 update release that has not yet reached RDP2 phase.If a requester thinks that a fix should reach the current JDK update release when it is already in RDP2 phase, then he needs to explicitly state this in the "Fix Request" comment and provide some reasoning for that. The approver will then decide and give the according directions. If and only if the approver explicitly approves a fix for RDP2, it may be pushed to the jdk11u repository. Eligible candidates for RDP2 exceptions would be fixes that Oracle has brought to their correspondent JDK11u 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 jdk11u in order to have the maintainers of the security fixes finish up their closed testing.

Fix Requests

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

Timelines

JDK 11.0.3 timeline

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

JDK 11.0.4 timeline

  • March 2019 jdk11u-dev forest open
  • Late May 2019 RDP2
  • Early July 2019 RC phase (code freeze)
  • Mid July 2019 GA

JDK 11.0.5 timeline

  • June 2019 jdk11u-dev forest open
  • Late August 2019 RDP2
  • Early October 2019 RC phase (code freeze)
  • Mid October 2019 GA

Advanced JBS filters

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

11.0.3:

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

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

11.0.4:

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

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

11.0.5:

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

...

 Approved critical fixes show up in this JBS filter (login required).

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.

Repositories

jdk11u-dev: Closed for rampdown. Pushes for 11.0.30 after jdk11u-fix-yes approval. Check here for clearance.

jdk11u: Frozen for release of 11.0.29.

Timelines

The release date follows the schedule of Oracle Critical Patch Updates as this is the date embargoed security fixes can be published.

Dates may be subject to change.

OpenJDK 11.0.29

  • Wednesday, June 4th 2025 : jdk11u-dev forest open (tag: jdk-11.0.29+0)
  • Friday, July 25th 2025: First build promotion jdk11u-dev→jdk11u (tag: jdk-11.0.29+1)
  • Friday, August 1st 2025: Skipped; no changes.
  • Friday, August 8th 2025: Second build promotion jdk11u-dev→jdk11u (tag: jdk-11.0.29+2).
  • Friday, August 15th 2025: Third build promotion jdk11u-dev→jdk11u (tag: jdk-11.0.29+3).
  • Friday, August 22nd 2025: Fourth build promotion jdk11u-dev→jdk11u (tag:jdk-11.0.29+4).
  • Friday, August 29th 2025: Fifth and final build promotion jdk11u-dev→jdk11u (tag:jdk-11.0.29+5). Start of Rampdown phase.
  • Friday, September 5th 2025: Skipped; no changes.
  • Friday, September 12th 2025: Skipped; no changes.
  • Friday, September 19th 2025: Skipped; no changes.
  • Friday, September 26th 2025: First and final jdk11u build promotion (tag: jdk-11.0.29+6). Frozen for release.
  • Tuesday, October 21st 2025: GA; OpenJDK 11.0.29 released (tag: jdk-11.0.29-ga, likely to bejdk-11.0.29+7)


Older releases can be found in the archive.

Downloads

Latest Generally Available (GA) binary releases of the jdk11u stream of the OpenJDK jdk-updates project are available at: https://adoptium.net/temurin/releases/?version=11

Latest Early Access (EA) binary releases of the jdk11u stream of the OpenJDK jdk-updates project are available at: https://adoptium.net/temurin/nightly/?version=11

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

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

Filters for Release 11.0.27

11.0.27/all: OracleJDK but not OpenJDK: Changes backported to OracleJDK 11.0.3-11.0.27 but not in OpenJDK 11.0.27.

11.0.27/all/!deferred: OracleJDK but not OpenJDK: Changes backported to OracleJDK 11.0.3-11.0.27 but not in OpenJDK 11.0.27 excluding deferred Items, see JBS labels below.

11.0.27/new/!deferred: OracleJDK but not OpenJDK: Changes new in OracleJDK 11.0.27 but not in OpenJDK 11.0.27 excluding deferred Items, see JBS labels below.

Common jdk11u JBS labels

The above filters exclude issues that are marked with the following labels:

  • jdk11u-na Change does not apply to open jdk11u. In general, this is a change done by Oracle for their build or test infrastructure, for their own delivery or in their tests not open sourced. Any other change can also be not of interest to open jdk11u. In the past, we also used label openjdk-na for this purpose.
  • jdk11u-jvmci-defer Changes that address jvmci and graal. We, the maintainers, currently do not backport these changes. Feel free to address them!
  • jdk11u-solaris-sparc-defer Changes that address the Solaris or sparc ports. We, the maintainers currently do not backport these changes. Feel free to address them!
  • jdk11u-a11y-defer Changes that address accessibility. These should be urgently backported.
  • jdk11u-nashorn-defer  Changes to the Nashorn java script engine.
  • jdk11u-defer-next Change is generally acceptable, but should go into the next JDK 11 update release. I.e. 11.0.29 is currently collecting fixes in jdk11u-dev, but the proposed change should get into 11.0.30 (the next release) instead.  The maintainers will clear this label when development of the next release (11.0.30 in the example) is started.
  • jdk11u-todo Changes Oracle backported to older releases that are not backported to open jdk11u.  We mostly need this tag to make the "all" filters more efficient.