From e7ea141ecc6ff93842c915395f1c14d3a3f69cf3 Mon Sep 17 00:00:00 2001
From: John Halley Gotway <johnhg@ucar.edu>
Date: Wed, 18 Nov 2020 11:08:31 -0700
Subject: [PATCH] Per #673, be sure to list the release date in conf.py.

---
 docs/Release_Guide/release_steps/met/update_version.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/Release_Guide/release_steps/met/update_version.rst b/docs/Release_Guide/release_steps/met/update_version.rst
index f87ea2a4ee..e00758cb70 100644
--- a/docs/Release_Guide/release_steps/met/update_version.rst
+++ b/docs/Release_Guide/release_steps/met/update_version.rst
@@ -5,7 +5,7 @@ To update the MET version number, start by writing a GitHub issue to describe th
 
 - Details for an official release (e.g. vX.Y)
   - Update the *met_version* variable in *met/src/basic/vx_util/util_constants.h* which defines the version number written to the MET output files.
-  - Update the *version* variable in *met/docs/conf.py* which defines the version number for the documentation.
+  - Update the *version*, *release_year*, and *release_date* variables in *met/docs/conf.py* which defines the version number for the documentation.
   - Update the version number in the locations listed above.
   - Update the version number listed in the MET configuration files:
     - Default configuration files in *met/data/config*.
@@ -16,11 +16,11 @@ To update the MET version number, start by writing a GitHub issue to describe th
 
 - Details for a bugfix release (e.g. vX.Y.Z)
   - Update the *met_version* variable in *met/src/basic/vx_util/util_constants.h* which defines the version number written to the MET output files.
-  - Update the *version* variable in *met/docs/conf.py* defines the version number for the documentation.
+  - Update the *version*, *release_year*, and *release_date* variables in *met/docs/conf.py* which defines the version number for the documentation.
   - Do *NOT* update the version number in the configuration files, add a new table file, or add a new test header file.
   
 - Details for a development release (e.g. vX.Y-betaN or vX.Y-rcN)
   - Prior to creating the first development release (e.g. beta1) for a new version, the official release version number should have already been updated.
   - If the official release version has not yet been updated (e.g. beta1), follow the official release instructions to do so.
   - If the official release version has already been updated (e.g. beta2 and beyond), do the following:
-    - Update the *version* variable in *met/docs/conf.py* which defines the version number for the documentation.
+    - Update the *version*, *release_year*, and *release_date* variables in *met/docs/conf.py* which defines the version number for the documentation.