The document explains semantic versioning, a software release numbering system that uses three numbers (major.minor.patch) to indicate version changes. It highlights the benefits of semantic versioning, such as improved clarity in compatibility and dependencies, and outlines how it handles major changes, new features, and bug fixes. Additionally, it covers pre-release versioning and provides a link for more information.

1. Semantic Versioning
A Software Release Numbering System

2. In This Tutorial
‣ Explain what Semantic Versioning is
‣ List the benefits
‣ Find more information

3. Semantic Versioning
‣ SemVer for short
‣ Uses three numbers for version instead of two
‣ Requires a public API

4. The Numbers
8.2.6
Major version
Minor version
Patch

5. The Numbers
8.2.6
Major version
Minor version
Patch
Major changes
Breaks the API

6. The Numbers
8.2.6
Major version
Minor version
Patch
Major changes
Breaks the API New features
Does not break API

7. The Numbers
8.2.6
Major version
Minor version
Patch
Bug fixesMajor changes
Breaks the API New features
Does not break API

8. The Numbers
8.2.6
Major version
Minor version
Patch
Bug fixesMajor changes
Breaks the API New features
Does not break API

9. Bug Fix
8.2.7

10. New Feature
8.3.0

11. Breaking the API
9.0.0

12. Pre-release Versioning
‣ Initial development uses Major version 0 (e.g. 0.1.0)
‣ You may use pre-release strings (e.g. alpha1, rc3, etc.)
• These are appended to the end (e.g. 1.0.0.alpha1)
‣ A publicly-released API starts at 1.0.0

13. Benefits of Semantic Versioning
‣ Clearer compatibility/dependencies
‣ Encourages well-defined APIs
‣ Makes upgrade decisions clearer

14. Specification
http://semver.org