[PROPOSAL] Formal policy around preserving dead methods with a warning

[Sean Farley]

Pierre-Yves David <pierre-yves.david at ens-lyon.org> writes:

> On 12/02/2015 03:50 PM, Augie Fackler wrote:
>>
>>> On Dec 2, 2015, at 6:37 PM, Laurent Charignon <lcharignon at fb.com> wrote:
>>>
>>>> Google and Facebook are known to have proprietary, internal extensions that we can’t even see the source to. Other organizations seem likely to have such setups as well, so it’s hard to proactively warn people about impending breakage (we can’t have our own buildbot or anything for those extensions.)
>>>
>>> I believe that all the extensions that we are using internally are on bitbucket (https://bitbucket.org/facebook/).
>>>
>>> I can't think of any extension that we have that is not there or in another public repo.
>>
>> Fair point. That said, I suspect extensions we don’t know about (proprietary or otherwise) are sources of pain for users at big organizations when things churn.
>
> Bitbucket have custom code that keep them from upgrading on a regular basis.

Just the in-memory merge stuff. Soon enough that will be in core!