3 ms·
How about incrementing the version number by an amount proportional to the lines that have changed in the code base. So 10% of lines have changed and 20% of lin
by simonh 8y ago
How about incrementing the version number by an amount proportional to the lines that have changed in the code base. So 10% of lines have changed and 20% of lines have been added, so increment version number from 5.6 to 7.28.
- laumars 8y agoLines of code are even less meaningful than version numbers. There are some good standards out there for versioning. But honestly the best thing you can do as a developer or sysadmin is to treat every version update like a breaking change and run it through your dev and test environments before pushing to prod.
- badsectoracula 8y agoWhat if you come up with a better algorithm for version 7.28 that is 80% shorter?
- yjftsjthsd-h 8y agoJust use the absolute value. An 80% decrease is a big change just like an 80% increase. (To be clear: I disagree with the suggestion, I just don't think this is a strong argument against it.)
- simonh 8y agoOne of my favourite Apple history anecdotes: https://www.folklore.org/StoryView.py?project=Macintosh&story=Negative_2000_Lines_Of_Code.txt https://www.folklore.org/StoryView.py?project=Macintosh&stor... With my tongue firmly still in my cheek, I'd say increment the version number by the difference. So if you deduct 5% of the code and add another 15%, then increment the version number by 20%.