"Major Version Numbers are Not Sacred" by Tom Preston-Werner https://tom.preston-werner.com/2022/05/23/major-version-numbers-are-not-sacred.html
This is a really interesting take, but I have mixed feeling about it.
"Major Version Numbers are Not Sacred" by Tom Preston-Werner https://tom.preston-werner.com/2022/05/23/major-version-numbers-are-not-sacred.html
This is a really interesting take, but I have mixed feeling about it.
I've worked on teams where any observable change is basically a breaking change, just because of how many people were using it (think spacebar heating https://xkcd.com/1172/). If we were being honest with ourselves, we'd bump the major every release.
And I've also dealt with tiny OSS libraries that flatter themselves by releasing 17 major versions in a year, forcing me to comb through their release notes to find they made some tiny innocuous change. There is no perfect way to do semver.
Although maybe these are two aspects of the same problem. Take the "spacebar heating" issue.
Hyrum's Law says that with a sufficient number of users, every observable change is a breaking change. So let's say you release 10 versions, and each version breaks 0.01% of your users.
It's very likely that none of those breaking changes affect me. And yet, I have to read 10 release notes before updating. And maybe those 0.01% of users are glad you bumped the major? But it sure annoys the rest of us.
@nolan btw isn't that blog post by the harasser who forced Julie Ann Horvath, one of GitHub's first woman employees, out of the company? https://en.wikipedia.org/wiki/Tom_Preston-Werner#Resignation_from_GitHub
Agreed that there is no perfect way to do semver
Chirp! is a social network. It runs on GNU social, version 2.0.1-beta0, available under the GNU Affero General Public License.
All Chirp! content and data are available under the Creative Commons Attribution 3.0 license.