The release cycle for release 11.0.<n> starts its initial stage in the jdk11u-dev repository as soon as the previous release enters its second stage and is confined to the jdk11u repository. The starting point is tagged with
jdk11.0.<n>+0. Once the previous release has happened, jdk11u-dev begins a cycle of being tagged on a weekly basis - when new changesets have been pushed - and the latest tag is promoted from jdk11u-dev to jdk11u. The tags have the format of
jdk11.0.<n>+<build>, where <n> is the placeholder for the update release and <build> is the monotonically increasing build number.
About 6 weeks before its release, or general availability (GA), an update release enters Rampdown. From that point onwards, the update release is stabilized by only accepting very select fixes in jdk11u, such as regressions, high priority issues and test fixes. Tagging again takes place on a weekly basis - when changes have occurred - but this time, it occurs in the opposite direction, with jdk11u changes being integrated back to jdk11u-dev. At the end of the month prior to the release month, a complete freeze will be announced for jdk11u, allowing the maintainers of the security changes (currently Red Hat) to integrate these into the repository and perform final testing of the collected fixes in a secure, internal environment. On release day, the final batch of changes will be pushed to jdk11u and the final tags jdk11tags
jdk11.0.<n>-ga will be set. To complete the process, jdk11u changes are integrated back into jdk11u-dev.