diff --git a/Release_Process.md b/RELEASE_PROCESS.md
similarity index 90%
rename from Release_Process.md
rename to RELEASE_PROCESS.md
index be4c448a..a12756a0 100644
--- a/Release_Process.md
+++ b/RELEASE_PROCESS.md
@@ -2,8 +2,14 @@
 
 The release process for BigchainDB server differs slightly depending on whether it's a minor or a patch release.
 
-BigchainDB follows [semantic versioning](http://semver.org/) (i.e. MAJOR.MINOR.PATCH), taking into account
-that [major version 0.x does not export a stable API](http://semver.org/#spec-item-4).
+BigchainDB follows 
+[the Python form of Semantic Versioning](https://packaging.python.org/tutorials/distributing-packages/#choosing-a-versioning-scheme)
+(i.e. MAJOR.MINOR.PATCH),
+which is almost identical
+to [regular semantic versioning](http://semver.org/)
+except release candidates are labelled like
+`3.4.5rc2` not `3.4.5-rc2` (with no hyphen).
+
 
 ## Minor release
 
@@ -14,6 +20,7 @@ A minor release is preceeded by a feature freeze and created from the 'master' b
 1. Create and checkout a new branch for the minor release, named after the minor version, without a preceeding 'v', e.g. `git checkout -b 0.9` (*not* 0.9.0, this new branch will be for e.g. 0.9.0, 0.9.1, 0.9.2, etc. each of which will be identified by a tagged commit)
 1. In `bigchaindb/version.py`, update `__version__` and `__short_version__`, e.g. to `0.9` and `0.9.0` (with no `.dev` on the end)
 1. Commit that change, and push the new branch to GitHub
+1. On GitHub, use the new branch to create a new pull request and wait for all the tests to pass
 1. Follow steps outlined in [Common Steps](#common-steps)
 1. In 'master' branch, Edit `bigchaindb/version.py`, increment the minor version to the next planned release, e.g. `0.10.0.dev`. This is so people reading the latest docs will know that they're for the latest (master branch) version of BigchainDB Server, not the docs at the time of the most recent release (which are also available).
 1. Go to [Docker Hub](https://hub.docker.com/), sign in, go to Settings - Build Settings, and under the build with Docker Tag Name equal to `latest`, change the Name to the number of the new release, e.g. `0.9`