Update release process with version schema

doc/release-process.md

@@ -4,15 +4,16 @@ Meta: There should always be a single release engineer to disambiguate responsib
 
 ## A. Define the release version as:
 
-    $ ZCASH_RELEASE=${UPSTREAM_VERSION}.z${ZCASH_RELEASE_COUNTER}
-    
+    $ ZCASH_RELEASE=MAJOR.MINOR.REVISION(-BUILD_STRING)
+
 Example:
 
-    $ ZCASH_RELEASE=0.11.2.z2
-    
-Also, the following commands use the ZCASH_RELEASE_PREV bash variable for the previous release:
+    $ ZCASH_RELEASE=1.0.0-beta2
 
-    $ ZCASH_RELEASE_PREV=0.11.2.z1
+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. update (commit) version in sources
@@ -21,8 +22,18 @@ Also, the following commands use the ZCASH_RELEASE_PREV bash variable for the pr
     src/clientversion.h
     configure.ac
     
-In `configure.ac` and `clientversion.h` change CLIENT_VERSION_IS_RELEASE to
-false while Zcash is in alpha-test phase.
+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.
 
 ### B2. write release notes