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”
The fairly mature internal component we’re working on is
v0.0.134.when the release notes just says “bug fixes”
“Various improvements”
I read this as pride as in
Pride versioning:
- LG
- LGB
- LGBT
- LGBTQ
- LGBTQI
- LGBTQIA
- LGBTQIA+
The + is just standing for
latestLGBTQIA-git
Lmao yes
Arch and queer, name a better duo
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
Date based version numbers is just lazy. There’s nothing more significant about a release in two weeks (2025.x.y) than today (2024.x.y).
At least with pride versioning there’s some logic to it.
