Add a draft of a release process document

The first draft is taken from
#355 (comment)

README.rst

@@ -151,3 +151,11 @@ Verification with Etherscan
     python -m raiden_contracts.deploy.etherscan_verify --apikey ETHERSCAN_APIKEY --contract-name SecretRegistry --chain-id 3
 
     python -m raiden_contracts.deploy.etherscan_verify --apikey ETHERSCAN_APIKEY --contract-name TokenNetworkRegistry --chain-id 3
+
+
+Making a Release
+----------------
+
+See `Release Process Document`_.
+
+.. _Release Process Document: RELEASE.rst

RELEASE.rst

@@ -0,0 +1,13 @@
+Release Process Document
+========================
+
+**This document has not been tested.**
+
+Outline of the release process
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+1. create and verify that contracts.json file matches the current source code
+2. deploy contracts with our deployment scripts and verify them on etherscan (we have a script for this that needs improvements)
+3. Step 2 also creates the deployment_*.json files automatically & also verifies the correctness of the info against the chain.
+4. Commit, make a PR
+5. Push the release tag on master directly -> this triggers the package release in travis; at this point everything should be checked and verified already by the CI tests (compiled data from contracts.json) and the checks that we have in place (deployment info, checks are in the deployment scripts)