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.
I read this as pride as in
Pride versioning:
- LG
- LGB
- LGBT
- LGBTQ
- LGBTQI
- LGBTQIA
- LGBTQIA+
Is + when they stop counting versions and just use a SaaS model?
The + is just standing for
latest
The fairly mature internal component we’re working on is
v0.0.134.when the release notes just says “bug fixes”
“Various improvements”
This is is basically just true
So pride is a synonym for semantic. Got it.
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”
Hey as long as it ships it can always be an RMA. If there’s a problem the customer will let us know™
That reminds me, maybe I should re-watch Doug Hickey’s full-throated attack on versioning & breaking changes. Spec-ulation Keynote
a classic
Thought it’s 2.7.1828182845904523536 for a sec
