Skip to content

Commit

Permalink
Feature 1746 recreate release (#1751)
Browse files Browse the repository at this point in the history
* Adding instructions for recreating and existing release

* Reorder the step's based on suggestions from @georgemccabe
  • Loading branch information
jprestop authored Aug 17, 2022
1 parent 64d5ee0 commit 91c1a65
Show file tree
Hide file tree
Showing 2 changed files with 23 additions and 1 deletion.
2 changes: 1 addition & 1 deletion docs/Release_Guide/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
22 changes: 22 additions & 0 deletions docs/Release_Guide/recreate_release.rst
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
Recreate an Existing Release
----------------------------

To recreate an existing development, bugfix, or official release:

* Reopen the corresponding development project from the
`Developmental Testbed Center organization project page <https://github.com/orgs/dtcenter/projects>`_.
* 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 <https://metplus.readthedocs.io/en/develop/Release_Guide/index.html#instructions-summary>`_,
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."


0 comments on commit 91c1a65

Please sign in to comment.