JDK 11 Updates [repo]

Maintainers

Andrew Haley (Lead Maintainer)

Fix Approvals and Push Policy

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

Changes that get approved (via the jdk11u-fix-yes label) have to be pushed to the jdk11u-dev repository. Those changes will then reach the next JDK 11 update release that has not yet reached RDP2 phase.

If a requester thinks that a fix should reach the current JDK update release when it is already in 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 directions. If and only if the approver explicitly approves a fix for RDP2, it may be pushed to the jdk11u repository. Eligible candidates for RDP2 exceptions would be fixes that Oracle has brought to their correspondent JDK11u release, P1 and P2 issues and test fixes.

Push Requests

[Outstanding requests] [All Requests] [All Approvals] [Approved requests without push]

Timelines

JDK 11.0.3 timeline

• Late February 2019 RDP2
• Mid April 2019 GA

JDK 11.0.4 timeline

• March 2019 jdk11u-dev forest open
• Late May 2019 RDP2
• Mid July 2019 GA

JDK 11.0.5 timeline

• June 2019 jdk11u-dev forest open
• Late August 2019 RDP2
• Mid October 2019 GA

Advanced JBS filters

The filters will only work for users that are logged into JBS.

11.0.3:

Open Downports Oracle -> OpenJDK: https://bugs.openjdk.java.net/issues/?filter=36366

Additional commits in OpenJDK vs. Oracle: https://bugs.openjdk.java.net/issues/?filter=36414

11.0.4:

Open Downports Oracle -> OpenJDK: https://bugs.openjdk.java.net/issues/?filter=36409

Additional commits in OpenJDK vs Oracle: https://bugs.openjdk.java.net/issues/?filter=36457