☆ Yσɠƚԋσʂ ☆ to Programmer Humor@lemmy.mlEnglish • 4 months agoPride Versioninglemmy.mlimagemessage-square34fedilinkarrow-up1599arrow-down12
arrow-up1597arrow-down1imagePride Versioninglemmy.ml☆ Yσɠƚԋσʂ ☆ to Programmer Humor@lemmy.mlEnglish • 4 months agomessage-square34fedilink
minus-square@Rogue@feddit.uklinkfedilink27•4 months agoI 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.
minus-square@Swedneck@discuss.tchncs.delinkfedilink4•4 months agoeither have meaning to the number and do semantic versioning, or don’t bother and simply use dates or maybe simple increments
minus-square@Rogue@feddit.uklinkfedilink3•4 months agoDate 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.
minus-square@Swedneck@discuss.tchncs.delinkfedilink2•4 months agothe point is just to have a way to tell releases apart, if every release is version 5 then you’re going to start self harming
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.
the point is just to have a way to tell releases apart, if every release is version 5 then you’re going to start self harming