From the Semver 2.0 FAQ:

>> Incompatible changes should not be introduced lightly to software that has a lot of dependent code.

Incorrect. It is better to release incompatible changes as soon as possible, to give people the most time to upgrade. Smaller releases mean smaller upgrade efforts.

Otherwise, this is why we have a Python 2.7.13.

Sign in to participate in the conversation

Generalistic and moderated instance.