Idea is not new, similar approach can be found in many places but now it has nice name. Lately I read Node Web Development and Node.js modules in npm used this approach to make npm so awesome. Read more at website: http://semver.org/ In a brief: There is API, it can be code or whatever but this is treated like API. Use 3 numbers: 1.2.3 - <major>.<minor>.<patch> Patch - bugifex - API comatible Minor - new or compatible API changes Major - any incompatible API changes How this can help? By using "strict" convention this can be used by tools (like npm) to make it easier to You to update dependencies. If You use library in version 1.2.0, then You can update easily it up to 2.0.0! Of course it is better co confirm it by developer that this really works, but if library developer uses semver like You, it should! There are many other rules, if You can't use it, at leas show it to You's co-workers, it would be great to really standardiz...