Outstanding approvals for critical fixes can be monitored here. The maintainers may approve with jdk11u-critical-yes, defer to jdk11u-dev or reject altogether. More minor bugs and new features should go in the next release being developed in jdk11u-dev. As the name of this tag suggests, this process is intended for fixes such as major regressions that must make the 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. 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 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).ĭuring the later stages of a release cycle, the release enters rampdown. Outstanding approvals can be monitored here. The maintainers will either approve by setting jdk11u-fix-yes or reject by setting jdk11u-fix-no. Push approval for a fix is requested by setting the jdk11u-fix-request label on the original JBS bug. 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. Please ask on the jdk-updates mailing list mailing list if you are in any doubt about whether your proposed backport might qualify. However, if there is an enhancement that provides substantial benefit to OpenJDK 11u users and it is of low risk, we will consider it. Changes necessary to make 11u work on new operating systems and hardware.Build system improvements, particularly for stability and reproducibility.Please note that these common rules do not allow enhancements to be back-ported, only fixes to bugs. In general we follow the common rules for the jdk-updates project. But by only doing that, you are at the grace of the community to pick up your suggestion. 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. 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. Exceptions are made if an issue only applies to 11.Įverybody is encouraged to submit fixes for OpenJDK 11 by creating a pull request to the jdk11u-dev Git repository. Most changes submitted to the OpenJDK 11 project will be backports from this repository. New fixes should first be submitted to the development repository for the current version of OpenJDK, jdk/jdk.

Distributors should use this as their primary source for creating OpenJDK builds.įor further process details you might want to continue reading here. 'the Tuesday closest to the 17th day of January, April, July and October.'ĭevelopment takes place in the jdk11u-dev Git repository and should be the primary place for OpenJDK committers to submit their work.Ĭode from the development repository is regularly tagged and promoted to the master jdk11u repository, which is used to stabilize and deliver the quarterly releases. OpenJDK 11 updates will be delivered on the same established quarterly cycle used by Oracle i.e. The list of Reviewers, Committers, and Authors can be found in the jdk updates section of the OpenJDK Census. OpenJDK 11 updates are part of the JDK updates project of the OpenJDK. Created by Robert Mckenna, last modified by Goetz Lindenmaier on Oct 18, 2023

Open jdk 11windows 64 bit