5.1. METplotpy Official Release
Create a new vX.Y.Z official release from the develop branch.
5.1.1. Open Release Issue
Define a new issue in the METplotpy repository to create the new release.
“Create the METplotpy vX.Y.Z release” for an official or bugfix release.
“Create the METplotpy vX.Y.Z-betaN (or -rcN) release” for a development release.
For an official or development release, assign the issue to the current METplotpy development project.
For a bugfix release, assign the issue to the organization level support project.
Select the target milestone.
5.1.2. Clone the Project Repository
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/METplotpy
Using HTTP:
git clone https://github.com/dtcenter/METplotpy
Enter the project repository directory:
cd METplotpy
5.1.3. Checkout the Develop Branch
Checkout the develop branch:
git checkout develop
5.1.4. Create Release Feature Branch
Create a feature branch in which to update the version number and add release notes being sure to include the GitHub issue number 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
5.1.5. Update Version Number for Release
Remove -dev from the version number:
We are naming releases with X.Y.Z format even if Z is 0.
The file containing the version number is located at docs/version.
In the develop branch, the version should match the upcoming release with -dev added to the end like X.Y.Z-betaN-dev, i.e. 4.0.0-beta1-dev
Remove -dev from the version number so that it matches the release you are creating.
Update the version number in the quick search links:
Open the docs/Users_Guide/quicksearch.rst file for editing.
Replace the word “develop” in all of the links with “vX.Y.Z”, replacing the X.Y.Z with the version number. For example, replace “develop” with “v4.0.0”.
Save and close the file.
5.1.6. Update Release Notes
You can refer to the GitHub Issues page to see what has changed for this release. Open the following URL in a browser:
https://github.com/dtcenter/METplotpy/issues
Click on the Projects tab and select the project (under Repository) that corresponds to the release you are creating.
Update the release-notes.rst file found in the User’s Guide directory.
When creating the official release, combine the beta release sections into one section (i.e. “Version X.Y.Z release notes (YYYYMMDD)”).
Commit changes and push to GitHub.
5.1.8. Merge Release Issue
After updating the version number and release notes on a release feature branch, submit a pull request to merge those changes back into the source branch.
5.1.9. Create Release Branch
Create a branch from the develop branch for the new official release and push it to GitHub.
cd METplotpy git checkout develop git pull git checkout -b main_vX.Y git push -u origin main_vX.Y
5.1.10. Push Release Branch to GitHub
Push the release branch to GitHub:
release_branch=main_vX.Y
git push origin $release_branch
5.1.11. Create Release on GitHub
Go to Releases on GitHub and click ‘Draft a new release’
Set the tag based on the version, starting with ‘v’, i.e. vX.Y.Z-betaN, vX.Y.Z-rcN, or vX.Y.Z
Set the branch value to ‘develop’ for a development release or ‘main_vX.Y’ for a bugfix or official release
Choose a release name (i.e. METplotpy-X.Y.Z-betaN, METplotpy-X.Y.Z-rcN, or METplotpy-X.Y.Z)
Add a link to the release notes from the METplotpy User’s Guide
Attach a PDF of the METplotpy User’s Guide, if available
If this is a development release, check the box that says “This is a pre-release”
Click on “Publish release”.
5.1.12. Update DTC Website
Navigate to the downloads page for the METplotpy repository at www.dtcenter.org.
Sign in to the Drupal interface and 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 “METplotpy Version X.Y.Z”.
For Related Community Code select both the METplus and the METplotpy options (use shift to select).
For Version Label type “METplotpy X.Y.Z betaN”.
Select the release type (Recommended for official or bugfix releases or Development for development versions). If necessary, change previously Recommended versions to Other.
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.
Add Link: Link text should be “Existing Builds and Docker” and the URL should be the latest Existing Builds page, i.e. https://dtcenter.org/community-code/metplus/metplus-4-0-existing-builds (If creating a new official release, be sure to add a new Existing Builds and Docker page, if one was not already created.)
Inside the text box in the “Release Notes” section provide a direct link to the release-notes.html file in the User’s Guide.
Click on “Create Release”.
Click on “Save”.
5.1.13. Finalize Release on GitHub
Close the GitHub issue for creating this official release.
Edit the milestone for the current release by updating the Due date with the actual release date.
If necessary, create a new milestone for the next official release (e.g. next vX.Y.Z release).
If necessary, reassign any remaining issues for the current milestone to the next one.
Close the current milestone.
Confirm that all existing development projects for the current milestone are closed.
If necessary, create development projects for the next milestone (e.g. METplotpy-X.Y.Z-beta1, beta2, beta3).
Update the repository settings by resetting the Default branch to the new main_vX.Y branch:
https://github.com/dtcenter/METplotpy -> Settings -> Branches (tab on left) -> change the drop down to new branch
5.1.14. Update Version Number for Release
Remove -dev from the version number:
We are naming releases with X.Y.Z format even if Z is 0.
The file containing the version number is located at docs/version.
In the develop branch, the version should match the upcoming release with -dev added to the end like X.Y.Z-betaN-dev, i.e. 4.0.0-beta1-dev
Remove -dev from the version number so that it matches the release you are creating.
Update the version number in the quick search links:
Open the docs/Users_Guide/quicksearch.rst file for editing.
Replace the word “develop” in all of the links with “vX.Y.Z”, replacing the X.Y.Z with the version number. For example, replace “develop” with “v4.0.0”.
Save and close the file.
5.1.15. Update the Documentation on the Web
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 Admin in the top menu
Click on Advanced Settings in the left menu
Select the new default branch in the dropdown menu for “Default branch” (e.g. main_v4.0.0)
Ensure that “latest” points to the new default branch by clicking on “View Docs”in the upper right corner and confirm that the version number displayed in the header is the desired version for “latest”.