Versioning is the way in which successive versions of the same software are identified using unique version names or unique version numbers.
Versioning is the way in which successive versions of the same software are identified using unique version names or unique version numbers.
Depending on how the software is distributed or deployed, it can have an internal (unpublished) version and an external (published release) version or just a single version.
A typical versioning scheme includes a numeric major and minor version separated by a dot. This scheme may be completed with a numeric or alphanumeric patch level or a build number.
Examples: 1.0
2.1
2.2a
2.2.27
Usage of the tag
If the question is about the use of the Semantic Versioning standard for API, prefer the tag semantic-versioning.
If the question is about the potential use of semantic versioning for other versioning purpose, use both tags versioning and semantic-versioning.
Do not use this tag for question about the management of source code versions; use version-control instead.
See also
- Software versioning article on Wikipedia
- What Is a Version Number and Why Is It Used? article on Lifewire
- Semantic versioning specifications
