News for hackers. Stuff that matters.
Re:Why we’re switching to calendar versioning by misterdoubt on Sunday April 14, 2019 @09:34AM (#19659319)
Yes! Semver is very precisely specified and the specification ain't very long. How on Earth could they mess it up?
Re:Why we’re switching to calendar versioning by lifthrasiir on Sunday April 14, 2019 @10:09AM (#19659505)
Because its summary does not exactly agree to the specification.

> Given a version number MAJOR.MINOR.PATCH, increment the: MAJOR version when you make incompatible API changes, MINOR version when you add functionality in a backwards-compatible manner, and PATCH version when you make backwards-compatible bug fixes.

Re:Why we’re switching to calendar versioning by knz42 on Sunday April 14, 2019 @10:07AM (#19659485)
A point not highlighted in OP article is that Enterprise customers are shy to upgrade to a "next major version" because they will _assume_ there are breaking changes in there (even though semver allows bumping the major number without breaking changes).

Calver side-steps this user bias.

Re:Why we’re switching to calendar versioning by AnIdiotOnTheNet on Sunday April 14, 2019 @10:36AM (#19659632)
Why are developers always insistent on trying to trick the user into doing what they want them to do, or what they think is best, instead of letting users do what users want to do?

Users shy away from major version numbers because they are allowed to change things in incompatible ways. When you jump a major version you're signaling that stuff might intentionally break, and they make their decisions accordingly. The solution is not to make your communication with user even worse!

Re:Why we’re switching to calendar versioning by soccerdave on Sunday April 14, 2019 @10:55AM (#19659749)
This could easily be solved by something along the lines of “Version 3.0 maintains full compatibility with Version 2.2” at the top of their release notes.

I dislike the idea of going away from SemVer just for marketing purposes. At least as a user when I’m going to upgrade versions then I could see that “oh, this version doesn’t break compatibility”

Re:Why we’re switching to calendar versioning by Dayshine on Sunday April 14, 2019 @04:02PM (#19661361)
>Calver side-steps this user bias.

Well, no, it just means users won't update at all, because every version could be breaking...