Commit f48658813ca86464aa76de4ff906c1ef47ddd863

Authored by Dmitriy Zaporozhets
2 parents 21649cab 13233d6d

Merge branch 'master' of gitlab.com:gitlab-org/gitlab-ce

Showing 2 changed files with 13 additions and 0 deletions   Show diff stats
README.md
... ... @@ -65,6 +65,8 @@
65 65  
66 66 * [Cloud 66 deployment and management](http://blog.cloud66.com/installing-gitlab-ubuntu/) Use Cloud 66 to deploy GitLab to your own server or any cloud (eg. DigitalOcean, AWS, Rackspace, GCE) and then manage it with database backups, scaling and more.
67 67  
  68 +* [Pkgr.io one-click installer](https://pkgr.io/apps/gitlabhq/gitlabhq) Currently supporting Ubuntu 14.04, Ubuntu 12.04 and Debian 7.4. For more information check the [README](https://gitlab.com/gitlab-org/gitlab-recipes/blob/master/install/pkgr/README.md) at gitlab-recipes repo.
  69 +
68 70 #### Unofficial installation methods
69 71  
70 72 * [GitLab recipes](https://gitlab.com/gitlab-org/gitlab-recipes/) repository with unofficial guides for using GitLab with different software (operating systems, webservers, etc.) than the official version.
... ...
doc/release/monthly.md
... ... @@ -201,6 +201,17 @@ Include a link to the blog post and keep it short.
201 201  
202 202 Proposed email for CE: "We have released a new version of GitLab Community Edition and its packages. See our blog post(<link>) for more information."
203 203  
  204 +### **10. Create a regressions issue**
  205 +
  206 +On [the GitLab CE issue tracker on GitLab.com](https://gitlab.com/gitlab-org/gitlab-ce/issues/) create an issue titled "GitLab X.X regressions" add the following text:
  207 +
  208 +This is a meta issue to discuss possible regressions in this monthly release and any patch versions.
  209 +Please do not raise issues directly in this issue but link to issues that might warrant a patch release.
  210 +The decision to create a patch release or not is with the release manager who is assigned to this issue.
  211 +The release manager will comment here about the plans for patch releases.
  212 +
  213 +Assign the issue to the release manager and /cc all the core-team members active on the issue tracker. If there are any known bugs in the release add them immediately.
  214 +
204 215 # **23rd - Optional Patch Release**
205 216  
206 217 # **24th - Update GitLab.com**
... ...