Per #2754, add a note to make the detail stand out better

dtcenter · Oct 28, 2024 · 7391d1e · 7391d1e
1 parent 238f7e1
commit 7391d1e
Show file tree

Hide file tree

Showing 3 changed files with 12 additions and 3 deletions.
diff --git a/docs/Release_Guide/release_steps/create_release_branch.rst b/docs/Release_Guide/release_steps/create_release_branch.rst
@@ -1,10 +1,13 @@
 Create Release Branch
 ^^^^^^^^^^^^^^^^^^^^^
 
-* These instructions only apply when creating the **first release candidate**
+.. note::
+
+  These instructions only apply when creating the **first release candidate**
   (rc1) development release. Skip this section for earlier beta (betaN) or later 
   release candidate (rc2+) development releases.
 
+
 * Create a new 'main_vX.Y' branch from the develop branch for the upcoming
   official release and push it to GitHub. All remaining development for the
   upcoming official release occurs on this new 'main_vX.Y' branch.

diff --git a/docs/Release_Guide/release_steps/met/create_release_reference_branch.rst b/docs/Release_Guide/release_steps/met/create_release_reference_branch.rst
@@ -1,10 +1,13 @@
 Create Release Reference Branch
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-* These instructions only apply when creating the **first release candidate**
+.. note::
+
+  These instructions only apply when creating the **first release candidate**
   (rc1) development release. Skip this section for earlier beta (betaN) or later 
   release candidate (rc2+) development releases.
 
+
 * Create a branch from the develop branch for the reference branch for the
   new official release and push it to GitHub. The branch name should match
   the format main_vX.Y-ref where X.Y is the major/minor release number.

diff --git a/docs/Release_Guide/release_steps/metplus/create_release_reference_branch.rst b/docs/Release_Guide/release_steps/metplus/create_release_reference_branch.rst
@@ -1,10 +1,13 @@
 Create Release Reference Branch
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-* These instructions only apply when creating the **first release candidate**
+.. note::
+
+  These instructions only apply when creating the **first release candidate**
   (rc1) development release. Skip this section for earlier beta (betaN) or later 
   release candidate (rc2+) development releases.
 
+
 * For METplus, the corresponding MET release must be created before starting
   this step. Specifically, a DockerHub tag on dtcenter/met that is named
   (X+6).Y-latest must already exist. For example, for METplus 4.1.0, the MET