4 files changed, 38 insertions, 2 deletions
diff --git a/doc/install/installation.md b/doc/install/installation.md
index a61a40ebd16..ca25eaea799 100644
--- a/doc/install/installation.md
+++ b/doc/install/installation.md
@@ -4,6 +4,12 @@
 
 Since an installation from source is a lot of work and error prone we strongly recommend the fast and reliable [Omnibus package installation](https://about.gitlab.com/downloads/) (deb/rpm).
 
+One reason the Omnibus package is more reliable is its use of Runit to restart any of the GitLab processes in case one crashes.
+On heavily used GitLab instances the memory usage of the Sidekiq background worker will grow over time.
+Omnibus packages solve this by [letting the Sidekiq terminate gracefully](http://doc.gitlab.com/ce/operations/sidekiq_memory_killer.html) if it uses too much memory.
+After this termination Runit will detect Sidekiq is not running and will start it.
+Since installations from source don't have Runit, Sidekiq can't be terminated and its memory usage will grow over time.
+
 ## Select Version to Install
 
 Make sure you view [this installation guide](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/install/installation.md) from the tag (version) of GitLab you would like to install.
diff --git a/doc/release/master.md b/doc/release/master.md
index 19070b46a0d..9163e652003 100644
--- a/doc/release/master.md
+++ b/doc/release/master.md
@@ -31,3 +31,32 @@ git remote add gl git@gitlab.com:gitlab-org/gitlab-ce.git
 gpa
 ```
 
+# Yanking packages from packages.gitlab.com
+
+In case something went wrong with the release and there is a need to remove the packages you can yank the packages by following the
+procedure described in [package cloud documentation](https://packagecloud.io/docs#yank_pkg).
+
+You need to have:
+
+1. `package_cloud` gem installed (sudo gem install package_cloud)
+1. Email and password for packages.gitlab.com
+1. Make sure that you are supplying the url to packages.gitlab.com (default is packagecloud.io)
+
+Example of yanking a package:
+
+```bash
+package_cloud yank --url https://packages.gitlab.com gitlab/gitlab-ce/el/6 gitlab-ce-7.10.2~omnibus-1.x86_64.rpm
+```
+
+If you are attempting this for the first time the output will look something like:
+
+```bash
+Looking for repository at gitlab/gitlab-ce... No config file exists at /Users/marin/.packagecloud. Login to create one.
+Email:
+marin@gitlab.com
+Password:
+
+Got your token. Writing a config file to /Users/marin/.packagecloud... success!
+success!
+Attempting to yank package at gitlab/gitlab-ce/el/6/gitlab-ce-7.10.2~omnibus-1.x86_64.rpm...done!
+```
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
diff --git a/doc/update/upgrader.md b/doc/update/upgrader.md
index 2cca46c86a3..d23534d58b6 100644
--- a/doc/update/upgrader.md
+++ b/doc/update/upgrader.md
@@ -73,4 +73,4 @@ cd /home/git/gitlab; \
   sudo service gitlab start; \
   sudo service nginx restart; \
   sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production
-```
+```
+\ No newline at end of file