From d16781ec3703503c88b5e41afe32055a1060b1fe Mon Sep 17 00:00:00 2001 From: Mayra Cabrera Date: Tue, 31 Jul 2018 12:06:28 -0500 Subject: [PATCH 1/2] Add a guide about to generate barometer section for Release blog post --- README.md | 1 + general/barometer-blog-post-section.md | 18 ++++++++++++++++++ 2 files changed, 19 insertions(+) create mode 100644 general/barometer-blog-post-section.md diff --git a/README.md b/README.md index 429e374a..27be32cb 100644 --- a/README.md +++ b/README.md @@ -63,6 +63,7 @@ does not apply when going over the deadline, so do not be late! - [How to create a blog post for a patch release](general/patch/blog-post.md) - [How to generate a QA issue](general/qa-issue-generation.md) - [How to handle exception requests](general/exception-request/process.md) +- [How to prepare barometer section for Release blog post?](general/barometer-blog-post-section.md) ## Further Reading diff --git a/general/barometer-blog-post-section.md b/general/barometer-blog-post-section.md new file mode 100644 index 00000000..c9fac4ef --- /dev/null +++ b/general/barometer-blog-post-section.md @@ -0,0 +1,18 @@ +# How to prepare Barometer section for Release blog post? + +The Barometer section describes the information about upgrading GitLab to the new version on the [Release post](https://about.gitlab.com/handbook/marketing/blog/release-posts/#release-posts). This is added by the Release Manager days in advanced before the 22nd, normally the Release Post Manager will ping the Release Managers so they can start working on this section. You can use the template presented in the [release post data file](https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/doc/templates/blog/YYYY_MM_DD_gitlab_x_y_released.yml#L178). + +The barometer section should include the following info: + +- How should the upgrade be done? Please detail. +- Do we expect downtime? If so, how long will it take? Please detail. +- Please detail migrations, post migrations, background migrations. Remember the times are posted in the #announcements channel on slack +- Are there any special cases, something important to note? Please detail. + +Note: It's important to have this section added with all the others, but, of course, it can be updated later if necessary. + +### Examples: + +- [Barometer section for 11.1](https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/13064) +- [Barometer section for 11.0](https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/12526) +- [Barometer section for 10.8](ttps://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/11716) -- GitLab From 90cf2e6c62d7f379be43453f475cc2091ba305f9 Mon Sep 17 00:00:00 2001 From: Mayra Cabrera Date: Fri, 3 Aug 2018 12:13:59 -0500 Subject: [PATCH 2/2] Improves grammar on barometer section --- README.md | 2 +- general/barometer-blog-post-section.md | 18 ------------------ .../barometer-section-for-release-blog-post.md | 18 ++++++++++++++++++ 3 files changed, 19 insertions(+), 19 deletions(-) delete mode 100644 general/barometer-blog-post-section.md create mode 100644 general/barometer-section-for-release-blog-post.md diff --git a/README.md b/README.md index 27be32cb..4837dde8 100644 --- a/README.md +++ b/README.md @@ -63,7 +63,7 @@ does not apply when going over the deadline, so do not be late! - [How to create a blog post for a patch release](general/patch/blog-post.md) - [How to generate a QA issue](general/qa-issue-generation.md) - [How to handle exception requests](general/exception-request/process.md) -- [How to prepare barometer section for Release blog post?](general/barometer-blog-post-section.md) +- [How to prepare barometer section for the Release blog post](general/barometer-blog-post-section.md) ## Further Reading diff --git a/general/barometer-blog-post-section.md b/general/barometer-blog-post-section.md deleted file mode 100644 index c9fac4ef..00000000 --- a/general/barometer-blog-post-section.md +++ /dev/null @@ -1,18 +0,0 @@ -# How to prepare Barometer section for Release blog post? - -The Barometer section describes the information about upgrading GitLab to the new version on the [Release post](https://about.gitlab.com/handbook/marketing/blog/release-posts/#release-posts). This is added by the Release Manager days in advanced before the 22nd, normally the Release Post Manager will ping the Release Managers so they can start working on this section. You can use the template presented in the [release post data file](https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/doc/templates/blog/YYYY_MM_DD_gitlab_x_y_released.yml#L178). - -The barometer section should include the following info: - -- How should the upgrade be done? Please detail. -- Do we expect downtime? If so, how long will it take? Please detail. -- Please detail migrations, post migrations, background migrations. Remember the times are posted in the #announcements channel on slack -- Are there any special cases, something important to note? Please detail. - -Note: It's important to have this section added with all the others, but, of course, it can be updated later if necessary. - -### Examples: - -- [Barometer section for 11.1](https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/13064) -- [Barometer section for 11.0](https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/12526) -- [Barometer section for 10.8](ttps://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/11716) diff --git a/general/barometer-section-for-release-blog-post.md b/general/barometer-section-for-release-blog-post.md new file mode 100644 index 00000000..76a92ed5 --- /dev/null +++ b/general/barometer-section-for-release-blog-post.md @@ -0,0 +1,18 @@ +# How to prepare Barometer section for the Release blog post + +The Barometer section describes how to upgrade GitLab to the new version on the [Release post](https://about.gitlab.com/handbook/marketing/blog/release-posts/#release-posts). This is added by the Release Manager days in advance before the 22nd. Normally the Release Post Manager will ping the Release Managers so they can start working on this section. You can use the template presented under the 'Upgrade barometer' section in the [release post data file](https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/doc/templates/blog/YYYY_MM_DD_gitlab_x_y_released.yml). + +The barometer section should include the following info: + +- How should the upgrade be done? +- Do we expect downtime? If so, how long will it take? +- States timing details about migrations, post migrations and background migrations. Remember that the timings are posted in the #announcements channel on slack. +- Are there any special cases, something important to note? + +Note: It's important to have this section added with all the others, but, of course, it can be updated later if necessary. + +### Examples: + +- [Barometer section for 11.1](https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/13064) +- [Barometer section for 11.0](https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/12526) +- [Barometer section for 10.8](ttps://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/11716) -- GitLab