summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMike Lewis <mlewis@gitlab.com>2019-01-23 01:32:38 +0000
committerMike Lewis <mlewis@gitlab.com>2019-01-23 01:32:38 +0000
commit5f902f1c89ffd6780f3efbe9afdebbef175fbb46 (patch)
treea65cc57852e0a86117e4f34005bd6d5d030241c5
parent1de38289e2fff116970febc50111b92d5ec877ff (diff)
downloadgitlab-ce-5f902f1c89ffd6780f3efbe9afdebbef175fbb46.tar.gz
Add clarity around meaning and potential range of version numbers
-rw-r--r--doc/policy/maintenance.md8
1 files changed, 5 insertions, 3 deletions
diff --git a/doc/policy/maintenance.md b/doc/policy/maintenance.md
index 6c3ad080e3e..1d656574acd 100644
--- a/doc/policy/maintenance.md
+++ b/doc/policy/maintenance.md
@@ -7,9 +7,11 @@ GitLab follows the [Semantic Versioning](http://semver.org/) for its releases:
For example, for GitLab version 10.5.7:
-- `10` represents major version.
-- `5` represents minor version.
-- `7` represents patch number.
+- `10` represents the major version. The major release was 10.0.0, but often referred to as 10.0.
+- `5` represents the minor version. The minor release was 10.5.0, but often referred to as 10.5.
+- `7` represents the patch number.
+
+Any part of the version number can increment into multiple digits, for example, 13.10.11.
The following table describes the version types and their release cadence: