Page History

Release Process

Right after update release 8u<n-1> was branched from mercurial repository jdk11u-dev to jdk11u, the The release cycle for release 11.0.<n> starts. As the very first step, the jdk11u-dev repository will be tagged with jdk11.0.<n>+0. One of the first changes should be to bump the version, e.g. something similar to JDK-8219710. At about 6 weeks 8u<n> starts its initial stage in the jdk8u-dev repository as soon as the previous release enters its second stage and is confined to the jdk8u repository. The starting point is tagged with jdk8u<n>-b00. Once the previous release has happened, jdk8u-dev begins a cycle of being tagged on a weekly basis - when new changesets have been pushed - and the latest tag is promoted from jdk8u-dev to jdk8u. The tags  have the format of jdk8u<n>-b<build>, where <n> is the placeholder for the update release and <build> is the monotonically increasing double digit build number.

About 6 weeks before its release, or before its general availability (GA), an update release enters ramp down phase 2 (RDP2) and the current state of jdk11u-dev will be transported to jdk11uenters Rampdown. From that point onwards, the update release is stabilized by only accepting very select fixes in jdk11u. Eligible candidates are fixes that Oracle has brought to their correspondent JDK11 update release, fixes for jdk8u, such as regressions, high priority issues or and test fixes. Builds from jdk11u will be tagged Tagging again takes place on a weekly basis , - when new changesets have been pushed. The tags will 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. Each tag that gets set in jdk11u will be integrated back to jdk11u-dev in a timely manner. At about 2 weeks before GAchanges have occurred - but this time, it occurs in the opposite direction, with jdk8u changes being integrated back to jdk8u-dev. At the end of the month prior to the release month, a complete freeze will be anounced for jdk11uannounced for jdk8u, allowing the maintainers of the security changes (currently Red Hat) to integrate and test these into the repository and perform final testing of the collected fixes in a secure, internal environment.  At the On release day, these the final batch of changes will be merged into jdk11u pushed to jdk8u and the final tags jdk11.0.<n>+<build> and jdk11.0.<n>tags jdk8u<n>-b<build> and jdk8u<n>-ga will be set. To complete the process, jdk8u changes are integrated back into jdk8u-dev.

Release

...

Engineers Checklist