2 ms·

Try Semantic Versioning [1]. It gives you a sane, well-defined way to version projects and makes the version numbers useful and meaningful. It makes it easy f

Try Semantic Versioning [1]. It gives you a sane, well-defined way to version projects and makes the version numbers useful and meaningful. It makes it easy for technical users and developers to get a feel for what has changed since the last time they updated. You don't have to display version numbers to non-technical users. The update summary in this post looks fantastic for showing what changes have been made to end users. [1]: http://semver.org/ http://semver.org/

latitude 15y ago
SemVer appears to be a formalization of a common versioning scheme as applied to APIs. And it inherits some of its problems. For example, > A bug fix is defined as an internal change that fixes incorrect behavior. One man's incorrect behavior is another man's proper working order. Excluding crashes, missing data and other obvious bloopers, the "bug fix" needs to be defined way more formally than this. That would lead to more strict documentation requirements, which is a major bore and inconvenience to any self-respecting developer, which in turn will lead to lapses in SemVer compliance and then back to the starting point :)