Update 'doc/release-process.md'

doc/release-process.md

@@ -30,17 +30,17 @@ git push
 The `--no-ff` flag above makes sure to make a merge commit, no matter what, even if a "fast forward" could be done. For those in the future looking back, it's much better to see evidence of when branches were merged.
 
 
-
 ### Git Issues
 
 Look for Git issues that should be fixed in the next release. Especially low-risk and simple things, like documentation changes, improvements to error messages and RPC help output. 
 
 ### Pre-release checklist:
-  * Is this release changing consensus rules?
+  * Is this release changing consensus rules? Definitely update protocol version.
 
 ### Protocol Safety Checks:
 
   * Does MIN_PROTO_VERSION need to change?
+    * If it does, new nodes will not be able to talk to nodes with a version less than MIN_PROTO_VERSION
 
 ## Release dependencies
 
@@ -50,4 +50,9 @@ Install deps on Linux:
 
 ## Release process
 
-...
+ - Update checkpoints
+ - Update man pages
+ - Update copyright years (if applicable) with replace.pl 
+ - Do a fresh clone and fresh sync with new checkpoints
+ - Stop node, wait 20 minutes, and then do a partial sync with new checkpoints
+