[11u] RFR(S): 8241234: Unify monitor enter/exit runtime entries.

[Andrew Haley]

On 08/09/2020 14:18, Andrew Haley wrote:
> On 08/09/2020 13:01, Lindenmaier, Goetz wrote:
>> One possibility to watch what Oracle is doing is that maintainers have
>> an eye on the according filters of 11.0.x-oracle changes and flag them
>> jdk11u-fix-no ad-hoc, before someone starts to actually work and
>> downport the bug.
>
> Looks good to me. But we'd first have to agree on the principle of
> not backporting some patches, and the criteria by which we'd decide.

Thinking about this some more: it really should be a reviewer's job to
object if a patch is likely to fail a risk-vs-reward test. Every patch
should be considered carefully in this way. It's hard for
inexperienced contributors to be able to make such judgements, so they
should ask on the list if it isn't clear.

But we can say this much: crashes and Java language specification
failures will always qualify for fixes; performance improvements,
especially small performance improvements, not so much. Compatibility
bugs which break communications protocols must be fixed. Updates for
new versions of communication protocols and new ciphers, probably.

There's a wide grey area in between, it's true.

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