This is is basically just true
I wish it was true here. Major releases are always the most shameful ones because so much is always left to “we can fix that later”
Thought it’s 2.7.1828182845904523536 for a sec
That reminds me, maybe I should re-watch Doug Hickey’s full-throated attack on versioning & breaking changes. Spec-ulation Keynote
The fairly mature internal component we’re working on is v0.0.134.
I once had someone open an issue in my side project repo who asked about a major release bump and whether it meant there were any breaking changes or major changes and I was just like idk I just thought I added enough and felt like bumping the major version ¯\_(ツ)_/¯
I think is the logic used for Linux kernel versioning so you’re in good company.
But everyone should really follow semantic versioning. It makes life so much easier.
either have meaning to the number and do semantic versioning, or don’t bother and simply use dates or maybe simple increments