Page History

...

Update fixes are collected in the jdk11u-dev repository repository and update releases will be stabilized in the jdk11u repository 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) 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 secure environment and tested internally at Red Hat 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.

...

In general we follow the common rules for the jdk-updates project.

Changes that get approved (via Push approval for a fix is requested by setting the jdk11u-fix-yes label) have to request label on the original bug. The maintainer will either approve by setting jdk11u-fix-yes or reject by setting jdk11u-fix-no. If and only if the fix gets approved, it may be pushed to the jdk11u-dev repository repository. Those changes It will then reach the next JDK 11 update release that has is not yet reached in RDP2 phase.

If a requester thinks that a fix should reach needs to be integrated into the current JDK 11 update release when it is already in after RDP2 phase, then he needs to explicitly state this in the "Fix Request" comment and provide some reasoning for that. The approver will then decide and give the according directionsthis can be requested via the jdk11u-critical-request label. The maintainer will approve with jdk11u-critical-yes or reject with jdk11u-critical-no. If and only if the approver explicitly approves a fix for RDP2fix gets approved, it may be pushed to the jdk11u repository. Eligible candidates for approval after RDP2 exceptions would be fixes that Oracle has brought to their correspondent JDK11u release, fixes for high priority issues and test fixes.

In the very last days before the release date, we won't accept any pushes to jdk11u in order to have the maintainers of the security fixes finish up their closed testing.internal testing.

Status

jdk11u-dev: Collecting 11.0.4 fixes. Pushes after jdk11u-fix-yes approval.

jdk11u: Collecting 11.0.3 fixes. Pushes after jdk11u-critical-yes approval.

Fix Requests

Standard

[Outstanding Unapproved requests] [All Requestsrequests] [All approved requests] [Approved requests without push]

Critical

[Unapproved critical requests] [All critical requests] [All critical approved requests] [Approved critical requests without push]

Timelines

JDK 11.0.3 timeline

...