- Loading...
For regular push requests, follow the guide instructions.
During the later stages of a release cycle, the release enters rampdown. If a change needs to be pushed to a release in rampdown, push approval can still be requested using the jdk25u-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. The maintainers may approve with jdk25u-critical-yes. Once the requester has pushed a critically approved fix it will automatically be included in the targeted release.
[Outstanding requests] [All Requests] [All Approvals]
JDK 25.0.1 timeline
JDK 25.0.2 timeline
This section applies to OpenJDK 25 starting with update 25.0.3.
OpenJDK 25 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 section of the OpenJDK Census.
OpenJDK 25 updates are delivered on the same established quarterly cycle used by Oracle i.e. "the third Tuesday of January, April, July and October."
Latest GA release: 25.0.1
Older releases can be found in the archive.
Latest Generally Available (GA) binary releases of the jdk25u stream of the OpenJDK jdk-updates project are available at: https://adoptium.net/temurin/releases/?version=25
Latest Early Access (EA) binary releases of the jdk25u stream of the OpenJDK jdk-updates project are available at: https://adoptium.net/temurin/nightly/?version=25
Development takes place in the jdk25u-dev Git repository. This is the primary place for OpenJDK committers to submit their work.
Code from the development repository is regularly tagged and promoted to the master jdk25u 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.
The release date follows the schedule of Oracle Critical Patch Updates as this is the date embargoed security fixes can be published.
OpenJDK 25.0.3
OpenJDK 25.0.4
OpenJDK 25.0.5
New fixes should first be submitted to the development repository for the current version of OpenJDK, jdk/jdk and then backported. Thus, most changes submitted to the OpenJDK 25 project will be backports from this repository. Exceptions are made if an issue only applies to 25.
Everybody is encouraged to submit fixes for OpenJDK 25 by creating a pull request to the jdk25u-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 25 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.
Don't prepare changes against repository jdk25u. Only in rare cases for urgent fixes during rampdown changes against jdk25u are possible (critical changes).
To assure a high quality of delivered updates, we restrict the scope of changes that are brought to jdk25u. In general we follow the common rules for the jdk-updates project, especially rule 3.
However, if there is an enhancement that provides substantial benefit to OpenJDK 25u users and it is of low risk, we will consider it. Please ask on the jdk-updates mailing list if you are in any doubt about whether your proposed backport might qualify.
The decision whether a change is suitable for jdk25u is taken by the maintaines in the approval process. If your change is ready for integration (implemented, tested, reviewed) you can trigger the approval with the /approval command in your pull request. In your approval comment, give the reason why you backport, your risk estimate, especially wrt. breaking existing installations, tell how you tested and whether a review was necessary. The maintainers try to guarantee weekly processing of outstanding approvals.
Some filters will only work for users that are logged into JBS.
These filters are used to process approval requests
Standard / jdk25u-dev targeted: [Unapproved requests] [Approved requests without push] [All requests] [Approved requests]
Critical / jdk25u targeted: [Unapproved requests] [Approved requests without push]
Whith these filters you can expore the differences between various releases.
Changes new in 25.0.3 excluding test changes: Differences to OpenJDK 25.0.2.
25.0.3/all: OpenJDK but not OracleJDK: Changes in OpenJDK 25.0.3 that are not in OracleJDK 25.0.3.
25.0.3/new: OracleJDK but not OpenJDK: Changes new in OracleJDK 25.0.3 but not in OpenJDK 25.0.3
Changes new in 25.0.4 excluding test changes tbd: Differences to OpenJDK 25.0.3.
25.0.4/all: OpenJDK but not OracleJDK tbd: Changes in OpenJDK 25.0.4 that are not in OracleJDK 25.0.4.
25.0.4/all: OracleJDK but not OpenJDK tbd: Changes backported to OracleJDK 25.0.3-25.0.4 but not in OpenJDK 25.0.4.
25.0.4/new: OracleJDK but not OpenJDK tbd: Changes new in OracleJDK 25.0.4 but not in OpenJDK 25.0.4
The above filters exclude issues that are marked with the following labels:
| weeks | jdk25u-dev | jdk25u |
|---|---|---|
| release of update n-1 | ||
| for two weeks after release of update n-1 | development of n ongoing | closed |
| 3-5 weeks | development of n ongoing | bulk merge from jdk25u-dev to jdk25u, tagging builds |
| 4 weeks | development of n+1 | public rampdown of update n, tagging |
| 3 weeks | development of n+1 | closed, rampdown of embargoed changes. |
| release of update n | ||