...
Update fixes are collected in the jdk11u-dev repository and update releases will be stabilized in the jdk11u repository. At the beginning of a release cycle, the jdk11u-dev repository will be tagged with jdk11.0.x+0, where x is a placeholder for the update release. At a certain point in time a release cycle enters ramp down phase 2 (RDP2) phase and jdk11u-dev will be transported to jdk11u. In jdk11u, stabilization is done by (only) accepting high priority or test fixes. jdk11u will be tagged on a weekly basis, when new changesets have been pushed. The tags will have the format of jdk11.0.x+n, where x is a placeholder for the update release and n is the monotonically increasing build number. At the release day, security changes that have been collected in a closed infrastructure by RedHat will be merged into jdk11u and the final tags jdk11.0.x+n and jdk11.0.x-ga will be set. Each tag that gets set in jdk11u will be integrated back to jdk11u-dev in a timely manner.
...