Page History

...

If it is recognized that a change should be backported when the CSR review of the feature release is initiated, the CSR for the feature release can also list multiple release for the update releases of interest, subject to the conventions described above.

Q: Doesn't backporting a CSR with SE Scope require special handling?
A: Yes; a CSR with a Scope of SE affects the Java SE specification. As such, it cannot be backported to an earlier release train as-is unless there is a maintenance review (MR) of the earlier release train's platform specification. Such MRs are uncommon, but do occur. It is sometimes possible for a CSR with SE Scope to be backported such that it does not have SE Scope, such as by only backporting an implementation change with a specification change mandating that changed behavior. In any case, any CSR with SE Scope should have explicit CSR review when being backported.

Q: Under what conditions does a CSR need to be filed for a purely behavioral change?
A: Using qualitative terms, a CSR for a behavioral change should be filed if it is estimated enough developers or users would be sufficiently impacted by the change that it should get additional consideration or documentation. A judgment call is involved. If assistance is needed in determining whether or not a CSR needs to be filed, ask the CSR representative for that area or the CSR chair.

...