From 297719b3e7285af4ff35171590d8a9da85a76981 Mon Sep 17 00:00:00 2001 From: Dilan Orrino Date: Sun, 29 Jan 2023 21:31:12 +0000 Subject: [PATCH 1/7] Added announcement of scheduled upgrades stops. --- doc/update/index.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/doc/update/index.md b/doc/update/index.md index b1d721835829d8..1fa3812de3f11e 100644 --- a/doc/update/index.md +++ b/doc/update/index.md @@ -182,6 +182,8 @@ If you don't want any downtime, read how to [upgrade with zero downtime](zero_do For a dynamic view of examples of supported upgrade paths, try the [Upgrade Path tool](https://gitlab-com.gitlab.io/support/toolbox/upgrade-path/) maintained by the [GitLab Support team](https://about.gitlab.com/handbook/support/#about-the-support-team). To share feedback and help improve the tool, create an issue or MR in the [upgrade-path project](https://gitlab.com/gitlab-com/support/toolbox/upgrade-path). +In 16.0 and forward, we will be scheduling required upgrade stops, either 1 or 2, through the course of the major release. GitLab will not implement a required upgrade stop without 3 milestones of notice. + Find where your version sits in the upgrade path below, and upgrade GitLab accordingly, while also consulting the [version-specific upgrade instructions](#version-specific-upgrading-instructions): -- GitLab From 3ddf9f02adda17619cb5fdd515c65b4c970392b6 Mon Sep 17 00:00:00 2001 From: Dilan Orrino Date: Sun, 7 May 2023 18:33:47 +0000 Subject: [PATCH 2/7] Updated commitment and added clarity --- doc/update/index.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/doc/update/index.md b/doc/update/index.md index 1fa3812de3f11e..fa878009ec1e3e 100644 --- a/doc/update/index.md +++ b/doc/update/index.md @@ -182,7 +182,9 @@ If you don't want any downtime, read how to [upgrade with zero downtime](zero_do For a dynamic view of examples of supported upgrade paths, try the [Upgrade Path tool](https://gitlab-com.gitlab.io/support/toolbox/upgrade-path/) maintained by the [GitLab Support team](https://about.gitlab.com/handbook/support/#about-the-support-team). To share feedback and help improve the tool, create an issue or MR in the [upgrade-path project](https://gitlab.com/gitlab-com/support/toolbox/upgrade-path). -In 16.0 and forward, we will be scheduling required upgrade stops, either 1 or 2, through the course of the major release. GitLab will not implement a required upgrade stop without 3 milestones of notice. +In 16.0 and forward, we will be scheduling required upgrade stops, either 2 or 3, through the course of the major release. GitLab will not implement a required upgrade stop without 2 milestones of notice. The first planned required upgrade stop will occur in 16.3, if nothing is introduced requiring an upgrade stop 16.3 will be treated as a regular upgrade. + +GitLab will give at least 3 milestones of notice when a required upgrade stop is going to be introduced. No more than 2 required upgrades (outside of the minor release before a major release) will be allowed during the span of a major release. Find where your version sits in the upgrade path below, and upgrade GitLab accordingly, while also consulting the -- GitLab From e4e1bb3bfae42615152a0f3bed9714d96861fb1f Mon Sep 17 00:00:00 2001 From: Peter Lu Date: Mon, 8 May 2023 15:43:33 +0000 Subject: [PATCH 3/7] Apply 1 suggestion(s) to 1 file(s) --- doc/update/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/update/index.md b/doc/update/index.md index fa878009ec1e3e..c90c34cebbdd49 100644 --- a/doc/update/index.md +++ b/doc/update/index.md @@ -182,7 +182,7 @@ If you don't want any downtime, read how to [upgrade with zero downtime](zero_do For a dynamic view of examples of supported upgrade paths, try the [Upgrade Path tool](https://gitlab-com.gitlab.io/support/toolbox/upgrade-path/) maintained by the [GitLab Support team](https://about.gitlab.com/handbook/support/#about-the-support-team). To share feedback and help improve the tool, create an issue or MR in the [upgrade-path project](https://gitlab.com/gitlab-com/support/toolbox/upgrade-path). -In 16.0 and forward, we will be scheduling required upgrade stops, either 2 or 3, through the course of the major release. GitLab will not implement a required upgrade stop without 2 milestones of notice. The first planned required upgrade stop will occur in 16.3, if nothing is introduced requiring an upgrade stop 16.3 will be treated as a regular upgrade. +In v16 release, we will be scheduling required upgrade stops, either 2 or 3, through the course of the major release. GitLab will not implement a required upgrade stop without 2 milestones of notice. The first planned required upgrade stop will occur in 16.3, if nothing is introduced requiring an upgrade stop 16.3 will be treated as a regular upgrade. GitLab will give at least 3 milestones of notice when a required upgrade stop is going to be introduced. No more than 2 required upgrades (outside of the minor release before a major release) will be allowed during the span of a major release. -- GitLab From 94db6ead3470542566d9806fa610c2aed0fe21ca Mon Sep 17 00:00:00 2001 From: Dilan Orrino Date: Mon, 8 May 2023 15:45:53 +0000 Subject: [PATCH 4/7] Fixed confusing sentence --- doc/update/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/update/index.md b/doc/update/index.md index c90c34cebbdd49..c6439cd06da2c2 100644 --- a/doc/update/index.md +++ b/doc/update/index.md @@ -182,9 +182,9 @@ If you don't want any downtime, read how to [upgrade with zero downtime](zero_do For a dynamic view of examples of supported upgrade paths, try the [Upgrade Path tool](https://gitlab-com.gitlab.io/support/toolbox/upgrade-path/) maintained by the [GitLab Support team](https://about.gitlab.com/handbook/support/#about-the-support-team). To share feedback and help improve the tool, create an issue or MR in the [upgrade-path project](https://gitlab.com/gitlab-com/support/toolbox/upgrade-path). -In v16 release, we will be scheduling required upgrade stops, either 2 or 3, through the course of the major release. GitLab will not implement a required upgrade stop without 2 milestones of notice. The first planned required upgrade stop will occur in 16.3, if nothing is introduced requiring an upgrade stop 16.3 will be treated as a regular upgrade. +In v16 release, we will be scheduling required upgrade stops, either 2 or 3, through the course of the major release. GitLab will not implement a required upgrade stop without 2 milestones of notice. The first planned required upgrade stop will occur in 16.3, if nothing is introduced requiring an upgrade stop, 16.3 will be treated as a regular upgrade. -GitLab will give at least 3 milestones of notice when a required upgrade stop is going to be introduced. No more than 2 required upgrades (outside of the minor release before a major release) will be allowed during the span of a major release. +No more than 2 required upgrades (outside of the minor release before a major release) will be allowed during the span of a major release. Find where your version sits in the upgrade path below, and upgrade GitLab accordingly, while also consulting the -- GitLab From f9e0ab8b536d5632ad93169c444065c5ab532bf4 Mon Sep 17 00:00:00 2001 From: Sam Wiskow Date: Thu, 25 May 2023 13:42:02 +0000 Subject: [PATCH 5/7] Apply 1 suggestion(s) to 1 file(s) --- doc/update/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/update/index.md b/doc/update/index.md index c6439cd06da2c2..461c9270c0bc52 100644 --- a/doc/update/index.md +++ b/doc/update/index.md @@ -184,7 +184,7 @@ For a dynamic view of examples of supported upgrade paths, try the [Upgrade Path In v16 release, we will be scheduling required upgrade stops, either 2 or 3, through the course of the major release. GitLab will not implement a required upgrade stop without 2 milestones of notice. The first planned required upgrade stop will occur in 16.3, if nothing is introduced requiring an upgrade stop, 16.3 will be treated as a regular upgrade. -No more than 2 required upgrades (outside of the minor release before a major release) will be allowed during the span of a major release. +No more than 2 required upgrades (outside of the minor release before a major release) will be planned during the span of a major release. Find where your version sits in the upgrade path below, and upgrade GitLab accordingly, while also consulting the -- GitLab From cd0d445875276fbe2d1973ebc5f0f276cb921030 Mon Sep 17 00:00:00 2001 From: Dilan Orrino Date: Thu, 25 May 2023 13:49:35 +0000 Subject: [PATCH 6/7] Added required stop definition --- doc/update/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/update/index.md b/doc/update/index.md index 461c9270c0bc52..f5f9423786549b 100644 --- a/doc/update/index.md +++ b/doc/update/index.md @@ -182,7 +182,7 @@ If you don't want any downtime, read how to [upgrade with zero downtime](zero_do For a dynamic view of examples of supported upgrade paths, try the [Upgrade Path tool](https://gitlab-com.gitlab.io/support/toolbox/upgrade-path/) maintained by the [GitLab Support team](https://about.gitlab.com/handbook/support/#about-the-support-team). To share feedback and help improve the tool, create an issue or MR in the [upgrade-path project](https://gitlab.com/gitlab-com/support/toolbox/upgrade-path). -In v16 release, we will be scheduling required upgrade stops, either 2 or 3, through the course of the major release. GitLab will not implement a required upgrade stop without 2 milestones of notice. The first planned required upgrade stop will occur in 16.3, if nothing is introduced requiring an upgrade stop, 16.3 will be treated as a regular upgrade. + A required stop is a version of GitLab that instances must upgrade to before proceeding to later versions because some background migrations needs to be finalized. In v16 release, we will be scheduling required upgrade stops, either 2 or 3, through the course of the major release. GitLab will not implement a required upgrade stop without 2 milestones of notice. The first planned required upgrade stop will occur in 16.3, if nothing is introduced requiring an upgrade stop, 16.3 will be treated as a regular upgrade. No more than 2 required upgrades (outside of the minor release before a major release) will be planned during the span of a major release. -- GitLab From 63d4b95b6fe173eca043c82af173bc49e8ecb0bb Mon Sep 17 00:00:00 2001 From: Evan Read Date: Wed, 7 Jun 2023 14:47:58 +0000 Subject: [PATCH 7/7] Apply 1 suggestion(s) to 1 file(s) --- doc/update/index.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/doc/update/index.md b/doc/update/index.md index f5f9423786549b..2bd9923ee08b03 100644 --- a/doc/update/index.md +++ b/doc/update/index.md @@ -182,9 +182,14 @@ If you don't want any downtime, read how to [upgrade with zero downtime](zero_do For a dynamic view of examples of supported upgrade paths, try the [Upgrade Path tool](https://gitlab-com.gitlab.io/support/toolbox/upgrade-path/) maintained by the [GitLab Support team](https://about.gitlab.com/handbook/support/#about-the-support-team). To share feedback and help improve the tool, create an issue or MR in the [upgrade-path project](https://gitlab.com/gitlab-com/support/toolbox/upgrade-path). - A required stop is a version of GitLab that instances must upgrade to before proceeding to later versions because some background migrations needs to be finalized. In v16 release, we will be scheduling required upgrade stops, either 2 or 3, through the course of the major release. GitLab will not implement a required upgrade stop without 2 milestones of notice. The first planned required upgrade stop will occur in 16.3, if nothing is introduced requiring an upgrade stop, 16.3 will be treated as a regular upgrade. +Required upgrade stops are versions of GitLab that you must upgrade to before upgrading to later versions. Required upgrade stops allow required background +migrations to finish. -No more than 2 required upgrades (outside of the minor release before a major release) will be planned during the span of a major release. +During GitLab 16.x, we are scheduling two or three required upgrade stops. We will give at least two milestones of notice when we +schedule a required upgrade stop. + +The first planned required upgrade stop is scheduled for GitLab 16.3. If nothing is introduced requiring an upgrade stop, GitLab 16.3 will be treated as a +regular upgrade. Find where your version sits in the upgrade path below, and upgrade GitLab accordingly, while also consulting the -- GitLab