summaryrefslogtreecommitdiff
path: root/doc/policy
diff options
context:
space:
mode:
authorEvan Read <eread@gitlab.com>2018-11-13 16:07:16 +1000
committerEvan Read <eread@gitlab.com>2019-01-08 12:21:09 +1000
commitd98560c1f5c54127d1a48c4c8e326bbf06c31c4b (patch)
treeb2d2fc26829e0a7b25da18d09a1e7e07ba1efed8 /doc/policy
parent710f2ec50c49d1e773acc20058ed584f1402de33 (diff)
downloadgitlab-ce-d98560c1f5c54127d1a48c4c8e326bbf06c31c4b.tar.gz
Make unordered lists conform to styleguidedocs/fix-unordered-list-style
- Also makes other minor Markdown fixes that were near the main fixes.
Diffstat (limited to 'doc/policy')
-rw-r--r--doc/policy/maintenance.md20
1 files changed, 10 insertions, 10 deletions
diff --git a/doc/policy/maintenance.md b/doc/policy/maintenance.md
index 03ba2ae8817..1b93cdb83ac 100644
--- a/doc/policy/maintenance.md
+++ b/doc/policy/maintenance.md
@@ -15,9 +15,9 @@ 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 major version
+- `5` represents minor version
+- `7` represents patch number
## Patch releases
@@ -55,13 +55,13 @@ cases you need to consider.
It is considered safe to jump between patch versions and minor versions within
one major version. For example, it is safe to:
-* Upgrade the patch version:
- * `8.9.0` -> `8.9.7`
- * `8.9.0` -> `8.9.1`
- * `8.9.2` -> `8.9.6`
-* Upgrade the minor version:
- * `8.9.4` -> `8.12.3`
- * `9.2.3` -> `9.5.5`
+- Upgrade the patch version:
+ - `8.9.0` -> `8.9.7`
+ - `8.9.0` -> `8.9.1`
+ - `8.9.2` -> `8.9.6`
+- Upgrade the minor version:
+ - `8.9.4` -> `8.12.3`
+ - `9.2.3` -> `9.5.5`
Upgrading the major version requires more attention.
We cannot guarantee that upgrading between major versions will be seamless. As previously mentioned, major versions are reserved for backwards incompatible changes.