Describe the Enhancement

During the Coordinated METplus Release 5.1 process, it became clear that some steps are duplicated across the components. Redoing or rechecking the same steps multiple times for each component is unclear and requires more coordination than is needed. This issue it review the official release instructions for the components and factor out any steps that can be moved into a Coordinated METplus Release checklist. These include creating the coordinated release announcement, removing development release announcements for all components from the DTC website, Zenodo version updates, sending an email to RAL-IT requesting the installation of the new versions in /usr/local, updating the information on the MET Download page under "Sample Script For Compiling External Libraries And MET" (if these instructions haven't moved to RTD), and perhaps others.

Time Estimate

4 hours?

Sub-Issues

Consider breaking the enhancement down into sub-issues.
None needed.

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

Define the source of funding and account keys here or state NONE.

Define the Metadata

Assignee

• Select engineer(s) or no engineer required: John HG with Julie and George as reviewers/conributors
• Select scientist(s) or no scientist required

Labels

• Select component(s)
• Select priority
• Select requestor(s)

Projects and Milestone

• Select Repository and/or Organization level Project(s) or add alert: NEED CYCLE ASSIGNMENT label
• Select Milestone as the next official version or Future Versions

Define Related Issue(s)

Consider the impact to the other METplus components.

• METplus, MET, METdataio, METviewer, METexpress, METcalcpy, METplotpy
  No impacts.

Enhancement Checklist

See the METplus Workflow for details.

• Complete the issue definition above, including the Time Estimate and Funding Source.
• Fork this repository or create a branch of develop.
  Branch name: feature_<Issue Number>_<Description>
• Complete the development and test your changes.
• Add/update log messages for easier debugging.
• Add/update unit tests.
• Add/update documentation.
• Add any new Python packages to the METplus Components Python Requirements table.
• Push local changes to GitHub.
• Submit a pull request to merge into develop.
  Pull request: feature <Issue Number> <Description>
• Define the pull request metadata, as permissions allow.
  Select: Reviewer(s) and Development issues
  Select: Repository level development cycle Project for the next official release
  Select: Milestone as the next official version
• Iterate until the reviewer(s) accept and merge your changes.
• Delete your fork or branch.
• Close this issue.