3.1. MET Official Release
Create a new vX.Y.Z official release from the develop branch.
3.1.1. Open Release Issue
Define a new GitHub issue for creating this new release.
Instructions
Define a new issue in the MET repository to create the new release.
“Create the MET vX.Y.Z release” for an official or bugfix release.
“Create the MET vX.Y.Z-betaN (or -rcN) release” for a development release.
For an official or development release, assign the issue to the corresponding MET development project.
For a bugfix release, assign the issue to the organization level support project.
Select the target milestone.
3.1.2. Clone the Project Repository
Clone the repository onto your local machine.
Instructions
Create and work in a new directory to ensure a fresh environment:
mkdir release-X.Y.Z
cd release-X.Y.Z
Run the clone command to obtain the repository.
Using SSH:
git clone git@github.com:dtcenter/MET
Using HTTP:
git clone https://github.com/dtcenter/MET
Enter the project repository directory:
cd MET
3.1.3. Checkout the Main Branch
Instructions
Checkout the main branch for the X.Y release. If you are creating the MET-X.Y.Z official or bugfix release, checkout main_vX.Y.
git checkout main_vX.Y
3.1.4. Create Release Feature Branch
Create a feature branch to update the version number and add release notes.
Instructions
Include the GitHub issue number in the feature branch for the new release.
git checkout -b feature_NNNN_vX.Y.Z # for an official or bugfix release
git checkout -b feature_NNNN_vX.Y.Z-betaN # for a development release
git checkout -b feature_NNNN_vX.Y.Z-rcN # for a development release
3.1.5. Update Version Number
Update the version number in the code and documentation.
Instructions
If necessary, update the ‘met_version’ variable in ‘src/basic/vx_util/util_constants.h’ which defines the version number written to the MET output files.
In ‘docs/conf.py’, update the ‘version’, ‘release_year’, and ‘release_date’ variables for the documentation.
In ‘docs/Users_Guide/installation.rst’, search for the X.Y version, replacing the current X.Y version with the official X.Y version, if necessary. Pay particular attention to the “Note” about the C++ standard and modify if necessary. The X.Y version number in the “Note” box should NOT change unless the default C++ standard changes.
If necessary, update the MET flowchart:
In ‘docs/Flowchart’, update ‘MET_flowchart.pptx’ to add a new version for this release.
Save and commit a PNG version of the flowchart named ‘MET_flowchart_vX.Y.Z.png’.
Copy the new flowchart version into ‘docs/Users_Guide/figure/overview-figure.png’.
If necessary, update the version number listed in the MET configuration files:
Default configuration files in ‘data/config’.
Sample configuration files in ‘scripts/config’.
Test configuration files, searching recursively, in ‘internal/test_unit/config’.
If necessary, add a new ‘data/table_files/met_header_columns_VX.Y.txt’ defining the columns names for this version.
If necessary, add a new ‘internal/test_unit/hdr/met_X_Y.hdr’ file defining the column names for this version for the test scripts.
3.1.6. Update Docker Image Workflow
Update the list of versions whose Docker images should be rebuilt on schedule.
Instructions
The Create Release Docker Images workflow is defined in ‘.github/workflows/release-docker-images.yml’.
In the ‘workflow_dispatch’ section, consider updating the default ‘release_version’ to be built.
In the ‘define-matrix’ job, update the ‘version_list’ for schedule events:
Add the new vX.Y.Z version to the list of versions.
For bugfix releases, remove the previous bugfix version, e.g. vX.Y.Z-1. Only the most recent ‘vX.Y.Z’ bugfix version for each ‘vX.Y’ release can be listed to avoid ambiguity when updating ‘X.Y-latest’ tags on Docker Hub.
For official releases, remove earlier versions only if their support has ended.
3.1.7. Update Release Notes
Update the release notes for this release.
Instructions
You can refer to the GitHub Project board to see what has changed for this release. Open the following URL in a browser:
https://github.com/orgs/dtcenter/projects
Click on the project that corresponds to this release, i.e. MET-X.Y.Z Development
Navigate to the “Closed Issues” tab. If this tab does not exist, see GitHub Projects to Manage Development to create it.
Update the release-notes.rst file found in the User’s Guide directory.
Consider organizing release notes into logical groups (e.g. Enhancements, Bugfixes, Documentation, etc.) and modifying GitHub issue titles for consistency. The release notes should match the GitHub issue titles, when possible.
Use your best judgement to apply bold formatting for any major or important changes.
When creating the official release, combine the beta release sections into one section (i.e. “Version X.Y.Z release notes (YYYYMMDD)”).
For the METplus repository, remove the development timeline information under the METplus Release Information section prior to creating the official release.
Commit changes and push to GitHub.
3.1.8. Update Upgrade Instructions
Update the upgrade instructions for this release.
Instructions
Occasionally, changes will be made to software that will require users to make changes to their configuration files in order to use the latest release. For example, when ensemble post-processing was added to Gen-Ens-Prod and removed from Ensemble-Stat, users were required to make changes in their configuration files.
Note
This section is not always applicable.
To alert the users to the necessary steps involved with the upgrade:
Update the Upgrade Instructions section of the release-notes.rst file found in the MET User’s Guide directory with the necessary information.
Add an “upgrade instructions” link next to the appropriate METplus component (MET) after “latest” and before “development” in the METplus Components Release Note Links section in the release-notes.rst file in the METplus User’s Guide in the METplus GitHub repository ONLY if there are Upgrade Instructions for this release.
3.1.10. Merge Release Issue
After updating the release-specific content on a release feature branch, submit a pull request to merge those changes back into the source branch.
3.1.11. Create Release on GitHub
Create the new release on GitHub.
Instructions
Ensure that any and all dependent releases for MET have been created according to Release Dependencies.
Go to Releases on GitHub and click ‘Draft a new release’
For ‘Choose a tag’, create a new tag based on the version, starting with ‘v’ (i.e. vX.Y.Z-betaN, vX.Y.Z-rcN, or vX.Y.Z)
Define the ‘Target’ branch as:
‘develop’ for a beta development release
‘main_vX.Y’ for a release candidate, bugfix, or official release
Define the ‘Release title’ based on the repository name and version, without a leading ‘v’ (i.e. MET-X.Y.Z-betaN, MET-X.Y.Z-rcN, or MET-X.Y.Z)
Add a link to the release notes from the MET User’s Guide, i.e. https://MET.readthedocs.io/en/vX.Y.Z-betaN/Users_Guide/release-notes.html (Note: the URL will not be active until the release is created) Refer to a previous release to easily copy and modify this information.
Add links to the HTML and PDF versions of the MET User’s Guide on ReadTheDocs. https://MET.readthedocs.io/_/downloads/en/vX.Y.Z-betaN/pdf/ (Note: the URL will not be active until the release is created) Refer to a previous release to easily copy and modify this information.
If this is a development release, check the box that says “This is a pre-release”.
Click on “Publish release”.
3.1.12. Update DTC Website
METplus software releases are announced on the DTC website. Add or update information about software releases on the website.
Instructions
Navigate to https://dtcenter.org and sign in to the Drupal interface.
Navigate to the downloads page for the MET repository at https://dtcenter.org/community-code/metplus/download
Click on the Edit button to edit the Downloads page.
Create a new Software Release for the newly released version by clicking on Add New Release.
For Full Title of Release type “MET Version X.Y.Z”.
For Related Community Code select both the “METplus” and the “MET” options (For Macs, hold the Command key to select both).
For Version Label type “MET X.Y.Z-betaN”.
Select the Release Type (“Recommended” for official or bugfix releases or “Development” for development versions).
Enter the Release Date.
Click on Add Code Download then click Add Link to add links for each of the following:
Add Link: Link text should be the name of the release and the URL should be the release page that was just created under the GitHub Releases tab.
Add Link: Link text should be “User’s Guide” and the URL should be the top level directory of the User’s Guide hosted on the web. Beta releases can use “develop” in the URL, but for official releases, please ensure the link uses the branch name (e.g. main_vX.Y) as opposed to the tag name (e.g. vX.Y.Z). For example, use “https://metplus.readthedocs.io/en/main_vX.Y/Users_Guide/” and NOT “https://metplus.readthedocs.io/en/vX.Y.Z/Users_Guide/”
Add Link: Link text should be “Existing Builds and Docker” and the URL should be the latest Existing Builds page. Beta releases can use “develop” in the URL, but for rcN and official releases, please ensure the link uses the branch name (e.g. main_vX.Y). For example, use https://metplus.readthedocs.io/en/main_vX.Y/Users_Guide/release-notes.html#existing-builds
In the Release Notes text box provide a direct link to the release-notes.html file in the User’s Guide.
Click on Create Release.
Update the existing releases, as needed.
For a development release, ensure the “Release Type” is set to Development and change any previous Development versions to Other.
For a bugfix or official release, change any previous Recommended versions to Other.
For an official release, remove the corresponding development releases.
Edit the “Coordinated METplus Version X.Y” software release.
For a bugfix release, update the existing link and text in the “Coordinated METplus-X.Y” release section with the X.Y.Z+1 information.
Make any other necessary website updates. For example, the flowchart at https://dtcenter.org/community-code/model-evaluation-tools-met/system-architecture.
Click on Save at the bottom of the page.
3.1.13. Finalize Release on GitHub
Return to GitHub to finalize the details of this release.
Instructions
Update issues:
Close the GitHub issue for creating this official release.
If necessary, reassign any remaining issues for the current milestone to other milestones.
Update milestones:
Edit the milestone for the current release by updating the Due date with the actual release date.
Close the current milestone.
Create a new milestone for the first bugfix release (e.g. first vX.Y.1 (bugfix) release).
If necessary, create a new milestone for the next official release (e.g. next vX.Y.Z release).
Update projects:
Close the existing development project for the current milestone.
If necessary, see GitHub Projects to Manage Development to create a development project for the next milestone.
Update branches:
Remove any remaining stale development branches from the new release.
Update the repository settings by resetting the Default branch to the new main_vX.Y branch:
https://github.com/dtcenter/MET -> Settings -> Scroll down to the Default branch section -> Click the stacked arrows button next to default branch name -> Select the new default branch from the dropdown list -> Click the Update button
3.1.14. Update Tar File Links
Tar files containing the source code for the libraries upon which MET depends are provided on the DTC website. Update the tar file links for each official release.
Instructions
On the DTC web server machine (i.e. mohawk) navigate to installation directory as the met_test user.
runas met_test
cd /d2/www/dtcenter/dfiles/code/METplus/MET/installation
Add a link for the newly created MET release to the METbaseimage version upon which it depends.
# Replace "A.B" with the METbaseimage version
# upon which the MET "X.Y" version depends
ln -sf tar_files.met-base.vA.B.tgz tar_files.met-vX.Y.tgz
Update the “latest” link for the newly created MET “X.Y” version.
# Replace "A.B" with the METbaseimage version
ln -sf tar_files.met-base.vA.B.tgz tar_files.latest.tgz
Confirm the result at https://dtcenter.ucar.edu/dfiles/code/METplus/MET/installation.
3.1.15. Update the Documentation on the Web
Update the default branch for Read the Docs.
Instructions
Because Read the Docs is configured to automate the building of new “main” branches in the METplus components’ repositories, nothing needs to be done to build the documentation for the new release. See the Read the Docs section for further information. For an official release, it is important to update the “Default branch” to this latest “main” branch. An administrator of the METplus component repository will need to do the following to update the default branch:
Log into their Read the Docs account
Click on the appropriate METplus component project
Click on Settings in the top right menu
Select the new default branch in the dropdown menu for “Default branch” (e.g. main_v4.0.0) and click the Save button at the bottom of the page
Ensure that “latest” points to the new default branch by clicking on “latest” build that just started and click on “Version latest” to view the build run. When it finishes running, click on “View Docs” on the right of the page and confirm that the version number displayed in the header is the desired version for “latest”.
3.1.16. Update Zenodo
Update the DOI for this official release.
Instructions
In the MET GitHub repository scroll down to the README file and check the MET Digital Object Identifier (DOI) on Zenodo. Use the zip file for the new MET release to create a new version on Zenodo.
3.1.17. Create a Reminder to Delete Stale Releases
Two weeks after the official release, remove stale development tags and releases.
Instructions
Help keep the GitHub repositories and DockerHub clean by removing beta/rc tags and releases created during development for this official release. Do not delete the tags/releases for this release right away. Please set a calendar reminder or schedule an email to be sent two weeks from the release date as a reminder to delete the tags/releases.
In GitHub, first delete all of the releases that contain beta or rc in the name, then delete all corresponding tags. Delete any beta/rc tags in DockerHub if applicable.