diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-03-05 12:07:48 +0000 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-03-05 12:07:48 +0000 |
commit | 5a6b36b60502c50ab59c0bc3c345793b70a3d548 (patch) | |
tree | 7cf2effbd48359b44970f8f345cfa12ce6843dfd /doc/user | |
parent | a76d34e6716aa8267111ecdcd21416e9dec3a08d (diff) | |
download | gitlab-ce-5a6b36b60502c50ab59c0bc3c345793b70a3d548.tar.gz |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/user')
-rw-r--r-- | doc/user/project/releases/index.md | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/user/project/releases/index.md b/doc/user/project/releases/index.md index 8294bb4f6e2..f6e35ab03db 100644 --- a/doc/user/project/releases/index.md +++ b/doc/user/project/releases/index.md @@ -28,6 +28,18 @@ There are several ways to create a Release: Start by giving a [description](#release-description) to the Release and including its [assets](#release-assets), as follows. +## Release versioning + +Release versions are manually assigned by the user in the Release title. GitLab uses [Semantic Versioning](https://semver.org/) for our releases, and we recommend you do too. Use `(Major).(Minor).(Patch)`, as detailed in the [GitLab Policy for Versioning](../../../policy/maintenance.md#versioning). + +For example, for GitLab version `10.5.7`: + +- `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 be multiple digits, for example, `13.10.11`. + ### Release description Every Release has a description. You can add any text you like, but we recommend |