4 ms·
> Calling it an incompatible change is perhaps a little strong. Definitions of backwards incompatibility are either tautological or disingenuous (provided we t
by pygy_ 9y ago
> Calling it an incompatible change is perhaps a little strong.
Definitions of backwards incompatibility are either tautological or disingenuous (provided we talk about documented behavior).
The right way to do that change would have been to allow both names without warnings in a point/minor release (with the docs stating where the project is headed), add the depreciation warning with the next semver major one, and remove the old name on the next next semver major release.
- mattzito 9y agoThat though is a really long lifecycle for a product that may have a six month qualification and burn-in periods for a production enterprise implementation . You’re basically saying a change of config file parameter should take a year-plus?
- morgo 9y agoMySQL releases are 2-3 years. So it would be 4-6 years wait in this case :-)