Page History

...

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.

...

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, it may be pushed to the jdk11u repository. Approved critical fixes show up in this JBS filter (login required).

...

jdk11u-dev: Always open repository for development of upcoming JDK 11 Update releases. Pushes after jdk11u-fix-yes approval. Check here for clearance.

jdk11u: Repository used for Rampdown of JDK 11 Update releases. Pushes only during 4-weeks rampdown period after jdk11u-critical-yes approval. Check here for clearance.

...