docs: Add a note how to do stable branch cherry-picking
Stable branches were introduced. This change will add a small hint on how
patches can be picked into stable branches.
@@ -89,3 +89,24 @@ The release process is mostly automatic and consists of the following steps:
5. Adjust the release details (draft, pre-release) as necessary at
<https://github.com/kubevirt/kubevirt/releases/tag/$TAG>
6. Sent a friendly announcement email to <kubevirt-dev@googlegroups.com>
+
+Stable Branches
+---------------
+
+For every release a barnch will be created following the pattern `release-x.y`.
+For now, community members can propose pull requests to be included into a
+stable branch.
+Those pull requests should be limited to bug fixes and must not be
+enhancements.
+
+Cherry picking can be used to pick a merge commit from the master branch
+to a stable branch:
+
+```bash
+git checkout release-0.6
+git cherry-pick $THE_MERGE_COMMIT_ID -m 1 -sx
+[release-0.6 acd756040] Merge pull request #1234 from great_person
+ Author: Bob Builder <builder@bob.com>
+ Date: Thu Jun 28 17:50:05 2018 +0300
+ 5 files changed, 55 insertions(+), 22 deletions(-)
+```
