Describe the Task

1. Move the METplus Release Notes section out of the Overview chapter and into it's own chapter (under Overview - chapter 2). Rename in the following way:

• 1.6 METplus Release Notes -> 2 METplus Release Information
• 1.6.1. METplus Components Release Note Links -> 2.1 METplus Components Release Note Links
• Combine "1.6.1.1. Release Notes - Latest Official Release" and "1.6.1.2. Release Notes - Development Release" for one bulleted list with the following format, for example, "MET (latest official, upgrade instructions, development)" where "latest official", "upgrade instructions", "development" are links, but "upgrade instructions" is only linked if it is applicable for that release.
• 1.6.2. METplus Wrappers Release Notes -> 2.2 METplus Wrappers Release Notes
• New section 2.3 METplus Wrappers Upgrade Instructions

2. Update the release guide to include instructions for each component to link to "upgrade instructions" (latest) if necessary for the release.
3. Ensure release notes link on DTC website still works.

Time Estimate

<1 day

Sub-Issues

Consider breaking the task down into sub-issues.

• Add a checkbox for each sub-issue here.

Relevant Deadlines

ASAP so ensemble changes can be made in upgrade instructions.

Funding Source

2792541

Define the Metadata

Assignee

• Select engineer(s) or no engineer required
• 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 PROJECT 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

Task 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 Linked 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.