☆ Yσɠƚԋσʂ ☆@lemmy.ml to Programmer Humor@lemmy.mlEnglish · 1 day agoPride Versioninglemmy.mlexternal-linkmessage-square28fedilinkarrow-up1515arrow-down12
arrow-up1513arrow-down1external-linkPride Versioninglemmy.ml☆ Yσɠƚԋσʂ ☆@lemmy.ml to Programmer Humor@lemmy.mlEnglish · 1 day agomessage-square28fedilink
minus-squareRogue@feddit.uklinkfedilinkarrow-up24·20 hours 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-up2·4 hours 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·4 hours 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.
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.