Semantic Versioning: Difference between revisions
| Line 19: | Line 19: | ||
==Major Version== | ==Major Version== | ||
The major versions start at 0, which means that the software is in development phase and no guarantees can be made about the stability and the backward compatibility of of the [[#Public_API|public API]]. The major version is set to 1 (and consequently minor and patch versions to 0.0) when the software is first released publicly. From that moment on, the major version is incremented when the a version that comes with backward-incompatible [[#Public_API|public API]] changes is released. | |||
==Minor Version== | ==Minor Version== | ||
Revision as of 20:03, 3 January 2020
External
Internal
Overview
Semantic versioning means attaching meaning to a version label. The version label is used to communicate how the piece of software it is attached to changed in relation to other versions of the same piece of software. The essential components of a semantic versioning-compliant version label are:
<major>.<minor>.<patch>[-pre-release-label][+build-metadata]
Concepts
Public API
The semantic versioning-compliant version labels carry meaning about the public API of the piece of software they are attached to. The public API describes how the software is consumed by its clients.
Major Version
The major versions start at 0, which means that the software is in development phase and no guarantees can be made about the stability and the backward compatibility of of the public API. The major version is set to 1 (and consequently minor and patch versions to 0.0) when the software is first released publicly. From that moment on, the major version is incremented when the a version that comes with backward-incompatible public API changes is released.
Minor Version
Patch
Pre-Release Version
Build Metadata
Version Lock
Version Promiscuity
Versioned Artifact Immutability
https://semver.org/#spec-item-3