Merge branch 'montly_doc_with_next_release_blog_article' into 'master'
Update monthly doc to mention wip blogpost for next release. See merge request !1697
This commit is contained in:
commit
469d6373d0
1 changed files with 8 additions and 4 deletions
|
@ -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).
|
||||
|
|
Loading…
Reference in a new issue