From cf97f669874872dc2edf005ab8aaad88aef701f7 Mon Sep 17 00:00:00 2001
From: Nathan Wilcox <nathan@z.cash>
Date: Fri, 19 May 2017 17:16:59 -0700
Subject: [PATCH] Remove portions of `./doc/release-process.md` now implemented
 in `make-release.py`.

---
 doc/release-process.md | 51 ++++++------------------------------------
 1 file changed, 7 insertions(+), 44 deletions(-)

diff --git a/doc/release-process.md b/doc/release-process.md
index 45dd3af22..f16325984 100644
--- a/doc/release-process.md
+++ b/doc/release-process.md
@@ -16,57 +16,20 @@ The following should have been checked well in advance of the release:
   - miniupnpc
   - OpenSSL
 
+If this release changes the behavior of the protocol or fixes a serious
+bug, verify that a pre-release PR merge updated `PROTOCOL_VERSION` in
+`version.h` correctly.
+
 
 ## Release process
 
-## A. Define the release version as:
+Run the release script:
 
-    $ ZCASH_RELEASE=MAJOR.MINOR.REVISION(-BUILD_STRING)
+    $ ./zcutil/make-release.py <RELEASE> <RELEASE_PREV>
 
 Example:
 
-    $ ZCASH_RELEASE=1.0.0-beta2
-
-Also, the following commands use the `ZCASH_RELEASE_PREV` bash variable for the
-previous release:
-
-    $ ZCASH_RELEASE_PREV=1.0.0-beta1
-
-## B. Create a new release branch / github PR
-
-### B1. Check that you are up-to-date with current master, then create a release branch.
-
-### B2. Update (commit) version and deprecation in sources.
-
-Update the client version in these files:
-
-    README.md
-    src/clientversion.h
-    configure.ac
-    contrib/gitian-descriptors/gitian-linux.yml
-
-In `configure.ac` and `clientversion.h`:
-
-- Increment `CLIENT_VERSION_BUILD` according to the following schema:
-
-  - 0-24: `1.0.0-beta1`-`1.0.0-beta25`
-  - 25-49: `1.0.0-rc1`-`1.0.0-rc25`
-  - 50: `1.0.0`
-  - 51-99: `1.0.0-1`-`1.0.0-49`
-  - (`CLIENT_VERSION_REVISION` rolls over)
-  - 0-24: `1.0.1-beta1`-`1.0.1-beta25`
-
-- Change `CLIENT_VERSION_IS_RELEASE` to false while Zcash is in beta-test phase.
-
-Update `APPROX_RELEASE_HEIGHT` and `WEEKS_UNTIL_DEPRECATION` in `src/deprecation.h`
-so that `APPROX_RELEASE_HEIGHT` will be reached shortly after release, and
-`WEEKS_UNTIL_DEPRECATION` is the number of weeks from release day until the
-deprecation target (as defined by the current deprecation policy).
-
-If this release changes the behavior of the protocol or fixes a serious bug, we may
-also wish to change the `PROTOCOL_VERSION` in `version.h`.
-
-Commit these changes. (Be sure to do this before building, or else the built binary will include the flag `-dirty`)
+    $ ./zcutil/make-release.py v1.0.8-1 v1.0.9
 
 Build by running `./zcutil/build.sh`.