Saturday, October 31, 2015

Semantic Versioning

If you notice, software development usually released their software product with some label or using version numbers. There is many ways of naming convention rules that developer use for their software label / version. I prefer to use numbering formatted as MAJOR.MINOR.PATCH as references and it look much professional, right? If you need more information, come and read guidance wrote by Tom Preston Werner (inventor of Gravatars and cofounder of GitHub) about semantic versioning at

As summary, just follow the rules:
  1. MAJOR version when you make incompatible API changes,
  2. MINOR version when you add functionality in a backwards-compatible manner, and
  3. PATCH version when you make backwards-compatible bug fixes.

No comments:

Post a Comment