Merge pull request #1434 from mrueg/release.md

RELEASE.md: Add missing bits to the release workflow

RELEASE.md

@@ -29,10 +29,13 @@ Maintaining the release branches for older minor releases happens on a best effo
     ```
     * All lines should be full sentences
   * kube-state-metrics image tag used in Kubernetes deployment yaml config.
-* Cut the new release branch, i.e., `release-1.2`, or merge/cherry-pick changes onto the minor release branch you intend to tag the release on
-* Cut the new release tag, i.e., `v1.2.0-rc.0`
+* Cut the new release branch, e.g. `release-1.2`, or merge/cherry-pick changes onto the minor release branch you intend to tag the release on
+* Cut the new release tag, e.g. `v1.2.0-rc.0`
+* Create a new **pre-release** on github
 * New images are automatically built and pushed to `gcr.io/k8s-staging-kube-state-metrics/kube-state-metrics`
-* Promote image by sending a PR to [kubernetes/k8s.io](https://github.com/kubernetes/k8s.io) repo. Follow the [example PR](https://github.com/kubernetes/k8s.io/pull/1260).
+* Promote image by sending a PR to [kubernetes/k8s.io](https://github.com/kubernetes/k8s.io) repository. Follow the [example PR](https://github.com/kubernetes/k8s.io/pull/1260). Use [cip-mm](https://github.com/kubernetes/release/tree/master/cmd/cip-mm) to update the manifest files in this repository, e.g. `cip-mm --base_dir=k8s.gcr.io --staging_repo=gcr.io/k8s-staging-kube-state-metrics --filter_tag='v2.0.0-rc.1'`
+* Create a PR to merge the changes of this release back into the master branch.
+* Once the PR to promote the image is merged, mark the pre-release as a regular release.
 
 ## Stable release