Create the MET-12.1.0 Beta1 Development Release

[JohnHalleyGotway]

Describe the Task

Since this is the first release in 2025, remember to update the copyright notices from 2024 to 2025 throughout.
Doing so should have no impact on the regression test output.

@jprestop asks if we really need to continue doing this every year? Could look into answering that question about whether the copyright notice needs to appear in every source code file? Or could we refer to a single one defined in a common location? But for this beta1 release, recommend simply updating the existing ones.

Time Estimate

4 hours

Sub-Issues

Consider breaking the task down into sub-issues.
None.

Relevant Deadlines

None.

Funding Source

NOAA Base 2782544

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 MET-X.Y.Z version, Consider for Next Release, or Backlog of Development Ideas
• For a MET-X.Y.Z version, select the MET-X.Y.Z Development project

Define Related Issue(s)

Consider the impact to the other METplus components.

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

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.
• 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: MET-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.