From 89d3028b20d769185b20d9af8e2e2f58d29667b8 Mon Sep 17 00:00:00 2001 From: Marin Jankovski Date: Fri, 13 Mar 2015 19:00:16 -0700 Subject: [PATCH] Update monthly doc to mention wip blogpost for next release. --- doc/release/monthly.md | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/doc/release/monthly.md b/doc/release/monthly.md index ec96be27f3f..cfe01896d8f 100644 --- a/doc/release/monthly.md +++ b/doc/release/monthly.md @@ -178,6 +178,10 @@ Update [installation.md](/doc/install/installation.md) to the newest version in Follow the [release doc in the Omnibus repository](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/release.md). This can happen before tagging because Omnibus uses tags in its own repo and SHA1's to refer to the GitLab codebase. +## Update GitLab.com with the stable version + +- Deploy the package (should not need downtime because of the small difference with RC1) +- Deploy the package for ci.gitlab.com ## Release CE, EE and CI @@ -199,10 +203,10 @@ Proposed tweet "Release of GitLab X.X & CI Y.Y! FEATURE, FEATURE and FEATURE < Consider creating a post on Hacker News. -## Update GitLab.com with the stable version - -- Deploy the package (should not need downtime because of the small difference with RC1) - ## Release new AMIs [Follow this guide](https://dev.gitlab.org/gitlab/AMI/blob/master/README.md) + +## Create a WIP blogpost for the next release + +Create a WIP blogpost using [release blog template](https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/doc/release_blog_template.md).