RFR 8231264: Disable biased-locking and deprecate all flags related to biased-locking

[Andrew Dinn]

On 21/11/2019 21:31, David Holmes wrote:
> On 20/11/2019 2:51 am, Doerr, Martin wrote:
>> I think deprecating before publishing an evaluation or at least having
>> a discussion is not appropriate.
> 
> Deprecation shows the intent that we (eventually) want to remove this
> and that people should try to avoid using it. If we don't actually
> deprecate it but just turn off then here is a likely scenario:

Who is this we? The premise of your scenario has built in the conclusion
that some of /us/ are questioning and thereby excluded our critique from
any chance of qualifying the proposed action.

If the existence of such a consensus is not clear (and I suggest that
this thread makes that plain) and the evidence for arriving at such a
consensus is not compelling (ditto) and if the rest of the scenario will
likely play out as you suggest then that is a strong reason to
re-address the decision to switch the feature off, whether or not it is
deprecated at the same time.

> Alternatively we deprecate in 14 and customer lets us know straight away
> that it is still useful.

Alternatively, we come up with better evidence that it needs switching
off (and, possibly, deprecating).

regards,


Andrew Dinn
-----------
Senior Principal Software Engineer
Red Hat UK Ltd
Registered in England and Wales under Company Registration No. 03798903
Directors: Michael Cunningham, Michael ("Mike") O'Neill