-
Notifications
You must be signed in to change notification settings - Fork 37
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Feature 1746 recreate release (#1751)
* Adding instructions for recreating and existing release * Reorder the step's based on suggestions from @georgemccabe
- Loading branch information
Showing
2 changed files
with
23 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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." | ||
|
||
|