Update release.md with milestone step

Author: awgreene

doc/design/release.md

@@ -1,14 +1,18 @@
 # Steps to create a new release
 
-## Step 0: Installing Requirements
+## Step 0: Review the Release Milestone
+If the release you plan to create corresponds with an existing [milestone](https://github.com/operator-framework/operator-lifecycle-manager/milestone/), make sure that all features have been committed. If a feature will not be added to the release be sure to remove it from the milestone.
 
+
+## Step 1: Installing Requirements
 Ensure you have `autoconf`, `automake`, and `libtool` installed. On Fedora, you can run
 
 ```
 dnf install autoconf automake libtool
 ```
 
-## Step 1: Verify Manifests
+
+## Step 2: Verify Manifests
 We need to ensure that `./manifests` folder is in sync with the templates in `deploy/chart/templates`.
 * Make sure you have a clean workspace. `git status` should show no change(s) or untracked file.
 * Make sure you pull the latest from `upstream`.
@@ -27,12 +31,12 @@ If you see change(s) in `./manifests` folder, then:
 * Consult the team and backport the changes in `./manifests` folder into the templates.
 
 
-## Step 2: Bump the Version
+## Step 3: Bump the Version
 * Bump the version in `OLM_VERSION` file. Make a new PR with this change only.
 * Wait until the PR has been merged.
 
 
-## Step 3: Setup Tag
+## Step 4: Setup Tag
 If git `push` is disabled on `upstream` repository in your fork, then clone this repository so that you can push to `master` directly.
 
 * Pull the latest.
@@ -50,8 +54,7 @@ git push origin 0.11.0
 
 * Confirm that new images have been built here: <https://quay.io/repository/operator-framework/olm?tab=builds>.
 
-
-## Step 3: Generate Manifests
+## Step 5: Generate Manifests
 * Make sure you have a clean workspace. `git status` should show no change(s) or untracked file.
 * Make sure you pull the latest from `upstream`.
 * Run `make release` on `master` branch.
@@ -61,7 +64,7 @@ Verify the following:
 * The image digest in manifest file(s) matches the new tag in `quay.io`.
 * `./manifests` folder only differs in version and image.
 
-## Step 4: Generate Changelog
+## Step 6: Generate Changelog
 Changelogs for OLM are generated using [GitHub Changelog Generator](https://github.com/github-changelog-generator/github-changelog-generator).
 
 You need to have `gem` installed on your workstation. Execute the following command to install `github-changelog-generator`.
@@ -82,20 +85,20 @@ github_changelog_generator -u operator-framework -p operator-lifecycle-manager -
 ```
 * Open a new PR with the changelog.
 
-## Step 5: Create a New GitHub Release
+## Step 7: Create a New GitHub Release
 * Create a new GtiHub release [here](https://github.com/operator-framework/operator-lifecycle-manager/releases/new)
 * Choose the new tag matching the version you created.
 * You can set `Title` to the same value as the tag name.
 * Add the generated `changelog` to the release description.
 * Save `draft` of the release.
 
 
-## Step 5: QuickStart
+## Step 8: QuickStart
 Edit the GitHub Release:
 * Upload the files `crds.yam`, `install.sh` and `olm.yaml` as release artifacts. These files are located in `deploy/upstream/quickstart`
 * Add install instruction, see an [example here](https://github.com/operator-framework/operator-lifecycle-manager/releases/tag/0.10.0#Install).
 
 
-## Step 6: Publish Release
+## Step 9: Publish Release
 * Ensure that all links are valid and works as expected.
-* Publish the release!
+* Publish the release!