diff options
| author | Marin Jankovski <marin@gitlab.com> | 2015-05-08 10:10:54 +0300 |
|---|---|---|
| committer | Marin Jankovski <marin@gitlab.com> | 2015-05-08 10:10:54 +0300 |
| commit | 0fc6f0b5d406f530e9ad8a35f0188536f6525cb9 (patch) | |
| tree | c8e868a773e9b6ab23b71aefc271155d2cac7ba4 | |
| parent | 8b25ff66346760c483c471a593f79e8a7271747c (diff) | |
| parent | 4164f6155ab91fe64d3b8cd66f5db23ba6005018 (diff) | |
Merge branch 'new-issue-after-release' into 'master'
new issue after release
See merge request !1810
| -rw-r--r-- | doc/release/patch.md | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/release/patch.md b/doc/release/patch.md index 4c7b471785f..a569bb3da8d 100644 --- a/doc/release/patch.md +++ b/doc/release/patch.md @@ -44,7 +44,7 @@ Create release tag and push to remotes: bundle exec rake release["x.x.x"] ``` -### Release +## Release 1. [Build new packages with the latest version](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/release.md) 1. Apply the patch to GitLab.com and the private GitLab development server @@ -53,3 +53,4 @@ bundle exec rake release["x.x.x"] 1. Send tweets about the release from `@gitlab`, tweet should include the most important feature that the release is addressing and link to the blog post 1. Note in the 'GitLab X.X regressions' issue that the patch was published (CE only) 1. [Create new AMIs](https://dev.gitlab.org/gitlab/AMI/blob/master/README.md) +1. Create a new patch release issue for the next potential release
\ No newline at end of file |