Update documentation related to changing the end-of-service halt.

Co-authored-by: Daira-Emma Hopwood <daira@jacaranda.org>

doc/release-process.md

@@ -145,6 +145,11 @@ Examples:
 Ordinarily, we choose a release height that is a couple hundred blocks in
 the future in order to give time for CI to run.
 
+If it is necessary that the version you are building reach its end-of-service
+halt in less time than the ordinary 16 weeks, it may be necessary to modify
+the value of the `RELEASE_TO_DEPRECATION_WEEKS` constant in `deprecation.h`
+prior to running `make-release.py`.
+
 ### Create, Review, and Merge the release branch pull request
 
 Review the automated changes in git:

src/deprecation.h

@@ -11,8 +11,9 @@
 
 // Deprecation policy:
 // Per https://zips.z.cash/zip-0200
-// Shut down nodes running this version of code, 16 weeks' worth of blocks after the estimated
-// release block height. A warning is shown during the 14 days' worth of blocks prior to shut down.
+// Shut down nodes running this version of code, `RELEASE_TO_DEPRECATION_WEEKS` weeks' worth
+// of blocks after the estimated release block height. A warning is shown during the 14 days'
+// worth of blocks prior to shut down.
 static const int APPROX_RELEASE_HEIGHT = 2619960;
 static const int RELEASE_TO_DEPRECATION_WEEKS = 10;
 static const int EXPECTED_BLOCKS_PER_HOUR = 3600 / Consensus::POST_BLOSSOM_POW_TARGET_SPACING;