# IT:AD:Semantic Versioning #



<callout type="Navigation" class="small">

* [[../|(UP)]]
{{indexmenu>.#2|nsort tsort}}
* See:
  * [[IT/AD/CalVer/]]


</callout>


<panel title="Summary">

* UseCases:
  * Not specifically for websites
  * it's for APIs against which dependencies can be declare (says it at top of spec).
    * https://news.ycombinator.com/item?id=13378637


 The concept is:

* Use Major for breaking changes.
* Use Minor for Backward compatible new features/updates
* Use Build for bug patches
* Don't use the last digit.


</panel>


## Notes ##

* Advantages:
  * Widely Accepted.
* Considerations:
  * `SemVer` doesn't address marketing needs directly. A new marketing cycle != a Breaking change.
    * Maybe that is to be added as Text metadata in the fourth field (eg: "2.04.00.v11-released")
  * Has some advantages over CalVer.
* Disadvantages:
  * Requires human input to increment Major, Minor (patch can be derived from a build counter or date).  
  

Note:

* Minor and Build


## Resources ##

* http://semver.org/
* http://haacked.com/archive/2011/10/24/semver-nuget-nightly-builds.aspx




~~DISCUSSION~~