Commit ad61a61304ea422462ef1f7e71da7f71d91f60b9

Authored by Dmitriy Zaporozhets
2 parents 43ac196d f8112381

Merge branch 'update-monthly-release-doc' into 'master'

Update monthly release doc

/cc @sytse @jacobvosmaer @marin
Showing 1 changed file with 15 additions and 0 deletions   Show diff stats
doc/release/monthly.md
... ... @@ -17,6 +17,10 @@ NOTE: This is a guide for GitLab developers. If you are trying to install GitLab
17 17  
18 18 #### 3. Do users need to update dependencies like `git`?
19 19  
  20 +- Check the [GitLab Shell version](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/lib/tasks/gitlab/check.rake#L782)
  21 +
  22 +- Check the [Git version](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/lib/tasks/gitlab/check.rake#L794)
  23 +
20 24 #### 4. Get latest code
21 25  
22 26 #### 5. Does GitLab shell need to be updated?
... ... @@ -72,3 +76,14 @@ After making the release branch new commits are cherry-picked from master. When
72 76 * Mention what GitLab is on the second line: GitLab is open source software to collaborate on code.
73 77 * Select and thank the the Most Valuable Person (MVP) of this release.
74 78 * Add a note if there are security fixes: This release fixes an important security issue and we advise everyone to upgrade as soon as possible.
  79 +
  80 +# Tweet
  81 +
  82 +Send out a tweet to share the good news with the world. For a major/minor release, list the features in short and link to the blog post.
  83 +
  84 +For a RC, make sure to explain what a RC is.
  85 +
  86 +A patch release tweet should specify the fixes it brings and link to the corresponding blog post.
  87 +
  88 +
  89 +
... ...