The unfortunate truth about calendar versioning is that it pushes devs and clients toward “freshness” instead of quality.
Same issue that we have in Apple’s design department: change for the sake of change.
Same issue that we have in Apple’s design department: change for the sake of change.
SemVer makes that situation worse, by requiring a bigger major release to break some part of the API. Other failure modes detailed here: https://sedimental.org/designing_a_version.html