From 5a6b36b60502c50ab59c0bc3c345793b70a3d548 Mon Sep 17 00:00:00 2001 From: GitLab Bot Date: Thu, 5 Mar 2020 12:07:48 +0000 Subject: Add latest changes from gitlab-org/gitlab@master --- doc/user/project/releases/index.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) (limited to 'doc/user') 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 -- cgit v1.2.1