I really had to fight for versioning. Everyone was just patch version here. Breaking changes in the API, new features, completely overhauled design? Well, it’s 0.6.24 instead of 0.6.23 now.
But gladly we’re moving away from version numbers alltogether. Starting next year it will be 2025.1.0 with monthly releases
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
latestLGBTQIA-git
I prefer LGBTQIA-bin, my computer was in the closet for 10 years so the git version takes too long to compile
Lmao yes
Arch and queer, name a better duo
The fairly mature internal component we’re working on is
v0.0.134.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™
when the release notes just says “bug fixes”
“Various improvements”
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
