Make use of METplus version lookup script

[georgemccabe]

dtcenter/METplus#2562 adds a coordinated release version number lookup table and script to determine corresponding version numbers of different METplus components. That issue notes that a METviewer issue should be created to make use of this script. It does not describe the details of how this script will be used for METviewer.

Describe the Enhancement

Make use of METplus script to determine version numbers. This requires more definition. Potential uses include:

• Obtain corresponding version numbers of other METplus Analysis tools like METdataio, METcalcpy, or METplotpy.
• Obtain METplus main_vX.Y branch to trigger METplus use case runs when changes are pushed to the METviewer main branch
• Others?

Time Estimate

Estimate the amount of work required here.
Issues should represent approximately 1 to 3 days of work.

Sub-Issues

Consider breaking the enhancement down into sub-issues.

• Add a checkbox for each sub-issue here.

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

Labels

• Review default alert labels
• Select component(s)
• Select priority
• Select requestor(s)

Milestone and Projects

• Select Milestone as a METviewer-X.Y.Z version, Consider for Next Release, or Backlog of Development Ideas
• For a METviewer-X.Y.Z version, select the METviewer-X.Y.Z Development project

Define Related Issue(s)

Consider the impact to the other METplus components.

• METplus, MET, METdataio, METviewer, METexpress, METcalcpy, METplotpy

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.
• 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 issue
  Select: Milestone as the next official version
  Select: METviewer-X.Y.Z Development project for development toward the next official release
• Iterate until the reviewer(s) accept and merge your changes.
• Delete your fork or branch.
• Close this issue.