cm0002@infosec.pub to Programmer Humor@programming.dev · 19 days agoPride Versioninginfosec.pubimagemessage-square72linkfedilinkarrow-up1940arrow-down110
arrow-up1930arrow-down1imagePride Versioninginfosec.pubcm0002@infosec.pub to Programmer Humor@programming.dev · 19 days agomessage-square72linkfedilink
minus-squareVibeSurgeon@piefed.sociallinkfedilinkEnglisharrow-up66arrow-down1·19 days agoUnder semantic versioning, you should really be ashamed of bumping the major number, since this means you went and broke backwards compatibility in some way.
minus-squareanton@lemmy.blahaj.zonelinkfedilinkarrow-up56·18 days agoYou have done something, that it’s worth breaking backwards compatibility over.
minus-squareSaapas@piefed.ziplinkfedilinkEnglisharrow-up11·18 days agoYeah I just forgot how the old stuff worked
minus-squaresunbeam60@feddit.uklinkfedilinkarrow-up21·18 days agoExcept from 0.x.x to 1.0.0. That one means you’re committed to keeping the API/format stable. At least how I think about it.
minus-squareDonkter@lemmy.worldlinkfedilinkarrow-up7·18 days agoBump the first number when you update to a version that breaks compatibility. Bump the second number when you make a change that people might want to revert back from Bump the third number for bug fixes.
Under semantic versioning, you should really be ashamed of bumping the major number, since this means you went and broke backwards compatibility in some way.
You have done something, that it’s worth breaking backwards compatibility over.
Yeah I just forgot how the old stuff worked
Except from 0.x.x to 1.0.0. That one means you’re committed to keeping the API/format stable. At least how I think about it.
Python agrees.
Bump the first number when you update to a version that breaks compatibility.
Bump the second number when you make a change that people might want to revert back from
Bump the third number for bug fixes.
Sir…