From 7d4a516ed06d5318ba9a695937de697608e6fcec Mon Sep 17 00:00:00 2001 From: Julie Prestopnik Date: Wed, 17 Aug 2022 09:46:28 -0600 Subject: [PATCH 1/2] Adding instructions for recreating and existing release --- docs/Release_Guide/index.rst | 2 +- docs/Release_Guide/recreate_release.rst | 22 ++++++++++++++++++++++ 2 files changed, 23 insertions(+), 1 deletion(-) create mode 100644 docs/Release_Guide/recreate_release.rst diff --git a/docs/Release_Guide/index.rst b/docs/Release_Guide/index.rst index 6cb9cb88ef..573eaa3ab5 100644 --- a/docs/Release_Guide/index.rst +++ b/docs/Release_Guide/index.rst @@ -78,7 +78,7 @@ Release instructions for each of the METplus components are described in the fol metplotpy metviewer metexpress - + recreate_release Indices and tables diff --git a/docs/Release_Guide/recreate_release.rst b/docs/Release_Guide/recreate_release.rst new file mode 100644 index 0000000000..980a493945 --- /dev/null +++ b/docs/Release_Guide/recreate_release.rst @@ -0,0 +1,22 @@ +Recreate an Existing Release +---------------------------- + +To recreate an existing development, bugfix, or official release: + +* Delete the existing release from GitHub. +* Delete the existing release tag (e.g. v11.0.0-beta2) from GitHub. +* Reopen the corresponding development project from the + `Developmental Testbed Center organization project page `_. +* Make an necessary additions to the existing project. For example, move + any newly completed issues and pull requests (e.g. from beta3 back to + beta2). +* Reopen the GitHub issue for creating the previously created release. +* Follow the instructions from the + `Release Guide `_, + being sure to update the release data for the actual release note. Consider + adding a note in description section for the GitHub release to indicate + that this release was re-created with an explanation. For example, "NOTE: + The MET-11.0.0-beta2 development release from 8/3/2022 has been + recreated to resolve a compilation issue." + + From 22aa6c8e81afb04d0458093b76300b102c1cf3df Mon Sep 17 00:00:00 2001 From: Julie Prestopnik Date: Wed, 17 Aug 2022 11:10:38 -0600 Subject: [PATCH 2/2] Reorder the step's based on suggestions from @georgemccabe --- docs/Release_Guide/recreate_release.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/Release_Guide/recreate_release.rst b/docs/Release_Guide/recreate_release.rst index 980a493945..0b3d847ac8 100644 --- a/docs/Release_Guide/recreate_release.rst +++ b/docs/Release_Guide/recreate_release.rst @@ -3,14 +3,14 @@ Recreate an Existing Release To recreate an existing development, bugfix, or official release: -* Delete the existing release from GitHub. -* Delete the existing release tag (e.g. v11.0.0-beta2) from GitHub. * Reopen the corresponding development project from the `Developmental Testbed Center organization project page `_. * Make an necessary additions to the existing project. For example, move any newly completed issues and pull requests (e.g. from beta3 back to beta2). * Reopen the GitHub issue for creating the previously created release. +* Delete the existing release from GitHub. +* Delete the existing release tag (e.g. v11.0.0-beta2) from GitHub. * Follow the instructions from the `Release Guide `_, being sure to update the release data for the actual release note. Consider