☆ Yσɠƚԋσʂ ☆@lemmy.ml to Programmer Humor@lemmy.mlEnglish · 2 days agoPride Versioninglemmy.mlimagemessage-square34fedilinkarrow-up1557arrow-down12
arrow-up1555arrow-down1imagePride Versioninglemmy.ml☆ Yσɠƚԋσʂ ☆@lemmy.ml to Programmer Humor@lemmy.mlEnglish · 2 days agomessage-square34fedilink
minus-squareRogue@feddit.uklinkfedilinkarrow-up26·2 days 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-squareSwedneck@discuss.tchncs.delinkfedilinkarrow-up4·1 day agoeither have meaning to the number and do semantic versioning, or don’t bother and simply use dates or maybe simple increments
minus-squareRogue@feddit.uklinkfedilinkarrow-up2·1 day 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-squareSwedneck@discuss.tchncs.delinkfedilinkarrow-up2·12 hours 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