CSR process for OpenJDK 11 and 8 Updates

Andrew Haley aph at redhat.com
Wed Aug 21 08:20:26 UTC 2019

On 8/20/19 9:21 PM, Martin Balao wrote:

> In my personal view, a new CSR process for each backport where the
> original enhancement/bug has a CSR will add unnecessary overhead.
> Particularly when there are no release-specific modifications. I.e.:
> backporting a change that introduces exactly the same system
> property to a previous release. The maintainer has control over what
> goes in, and can take the existing CSR documentation as an input to
> make a decision on the approval request.


> I suggest that we only start a new CSR process when there are
> release-specific changes introduced. That can be informed as part of
> the "Fix Request" comment.

It depends on what the change does. It is not particularly unlikely
that a change which was appropriate for head might break jdk 11. In
that case a CSR is necessary. The CSR process is for us to use, not a

Andrew Haley  (he/him)
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671

More information about the jdk8u-dev mailing list