Am 31. Oktober 2015 02:52:01 MEZ, schrieb Matthew Brush <notifications@github.com>:

[...] so unless there are actual problems I don't see an evidence to keep the off default.

I mentioned a number of issues with it in the mailing list thread linked from the PR you made to disable it by default.

I don't think we should cram this in just because of string freeze, especially with the open issues, the UI issues, and that we will be releasing again in a few months. I'm not opposed to the feature, I'm opposed to the implementation (re-using an existing feature to do something else, something unexpected of the existing feature, as well as the infobar without a checkbox that can be hidden from the user without ever seeing it).

—
Reply to this email directly or view it on GitHub.


Carrying this discussion to the ML.

Can you elaborate on the issues you see?

As to the UI. It's important that we get any UI for 1.26, therefore we had to manage before string freeze. We can introduce a better UI fir 1.27. I'm not opposed to a check box but would be more effort. And it would presumably checked by default anyway, no?