summaryrefslogtreecommitdiff
path: root/doc/policy
diff options
context:
space:
mode:
authorGitLab Bot <gitlab-bot@gitlab.com>2020-03-23 03:09:21 +0000
committerGitLab Bot <gitlab-bot@gitlab.com>2020-03-23 03:09:21 +0000
commit5b51129e3356a12283f0ba2da15db897ee30cf1a (patch)
tree81aab0c51c265782c093da49f089908761d5426d /doc/policy
parent71da67f3262eeffe59cc228986e0a2bb97b6dba5 (diff)
downloadgitlab-ce-5b51129e3356a12283f0ba2da15db897ee30cf1a.tar.gz
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/policy')
-rw-r--r--doc/policy/maintenance.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/policy/maintenance.md b/doc/policy/maintenance.md
index 441360aa812..e9311285ba5 100644
--- a/doc/policy/maintenance.md
+++ b/doc/policy/maintenance.md
@@ -5,7 +5,7 @@ type: concepts
# GitLab Release and Maintenance Policy
GitLab has strict policies governing version naming, as well as release pace for major, minor,
-patch and security releases. New releases are usually announced on the [GitLab blog](https://about.gitlab.com/blog/categories/releases/).
+patch and security releases. New releases are usually announced on the [GitLab blog](https://about.gitlab.com/releases/categories/releases/).
Our current policy is:
@@ -103,13 +103,13 @@ Security releases are a special kind of patch release that only include security
fixes and patches (see below) for the previous two monthly releases in addition to the current stable release.
For very serious security issues, there is
-[precedent](https://about.gitlab.com/blog/2016/05/02/cve-2016-4340-patches/)
+[precedent](https://about.gitlab.com/releases/2016/05/02/cve-2016-4340-patches/)
to backport security fixes to even more monthly releases of GitLab.
This decision is made on a case-by-case basis.
## Upgrade recommendations
-We encourage everyone to run the [latest stable release](https://about.gitlab.com/blog/categories/releases/) to ensure that you can
+We encourage everyone to run the [latest stable release](https://about.gitlab.com/releases/categories/releases/) to ensure that you can
easily upgrade to the most secure and feature-rich GitLab experience. In order
to make sure you can easily run the most recent stable release, we are working
hard to keep the update process simple and reliable.