...
Push approval for a fix is requested by setting the jdk17u-fix-request label on the original JBS bug. The maintainers will either approve by setting jdk17u-fix-yes or reject by setting jdk17u-fix-no. Outstanding approvals can be monitored here TODO. If and only if the fix gets approved, it may be pushed to the jdk17u-dev repository. Approved fixes show up in this JBS filter TODO (login required).
During the later stages of a release cycle, the release enters rampdown. The master jdk17u repository contains the latest version of that release, while the jdk17u-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 jdk17u-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 jdk17u-dev. The maintainers may approve with jdk17u-critical-yes, defer to jdk17u-dev or reject altogether. Outstanding approvals for critical fixes can be monitored here TODO . If, and only if, the fix gets approved with jdk17u-critical-yes, it may be pushed to the jdk17u repository. Approved critical fixes show up in this JBS filter TODO (login required).
At the end of the month prior to the release month, the jdk17u 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 jdk17u repository and source bundles made available.
...
jdk17u-dev: Always open repository for development of upcoming JDK 17 Update releases. Pushes after jdk17u-fix-yes approval. Check here TODO for clearance.
jdk17u: Repository used for Rampdown of JDK 17 Update releases. Pushes only during 4-weeks rampdown period after jdk17u-critical-yes approval. Check here TODO for clearance.
Timelines
OpenJDK 17.0.3
...