☆ Yσɠƚԋσʂ ☆@lemmy.ml to Programmer Humor@lemmy.mlEnglish · 2 months agoPride Versioninglemmy.mlimagemessage-square5fedilinkarrow-up10arrow-down10
arrow-up10arrow-down1imagePride Versioninglemmy.ml☆ Yσɠƚԋσʂ ☆@lemmy.ml to Programmer Humor@lemmy.mlEnglish · 2 months agomessage-square5fedilink
minus-squareRogue@feddit.uklinkfedilinkarrow-up0·2 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-squareSwedneck@discuss.tchncs.delinkfedilinkarrow-up0·2 months 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-up1·2 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.
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.