Per #2751, this work was actually completed already, adding text to m…

…ake the directions more clear. (#2776)
dtcenter · Nov 7, 2024 · 17fdbef · 17fdbef
1 parent 0b51a13
commit 17fdbef
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 3 deletions.
diff --git a/docs/Release_Guide/release_steps/update_release_notes_development.rst b/docs/Release_Guide/release_steps/update_release_notes_development.rst
@@ -30,7 +30,9 @@ release. Open the following URL in a browser:
 * If you are creating a betaX release, add a new betaX section above the betaX-1
   release.
 
-* For the METplus repository, update the **development timeline**.
+* For the METplus repository, update the **development timeline** under the
+  `METplus Release Information <https://metplus.readthedocs.io/en/develop/Users_Guide/release-notes.html#metplus-release-information>`_
+  section.
 
   * If you are creating a beta1 release, add development timeline
     information with approximate dates for planned development cycles.

diff --git a/docs/Release_Guide/release_steps/update_release_notes_official.rst b/docs/Release_Guide/release_steps/update_release_notes_official.rst
@@ -26,7 +26,8 @@ release. Open the following URL in a browser:
 * When creating the official release, combine the beta release sections
   into one section (i.e. "Version X.Y.Z release notes (YYYYMMDD)").
 
-* For the METplus repository, remove the **development timeline** information
-  prior to creating the official release.
+* For the METplus repository, remove the **development timeline** information under the 
+  `METplus Release Information <https://metplus.readthedocs.io/en/develop/Users_Guide/release-notes.html#metplus-release-information>`_
+  section prior to creating the official release.
 
 * Commit changes and push to GitHub.