10. Creating a Release

10.1. Overview

When we put out a new release we should tag the repository and create a release. We will describe creating a release by way of example using the steps used to create the 3.0.1 release.

10.2. Tagging the release

To create a release you will first create a tag using git commands. You should get the short SHA for the release that can be found on the splash screen of any of the binaries built from the source tar file. The Linux distributions are all built with the source tar file. The Windows distribution is typically not. To bring up the splash screen go to Help->About.


Fig. 10.28 The splash screen with the short SHA.

Now you can issue the git commands to create the tag and push it to GitHub.

git checkout 3.0RC
git checkout 2f38385
git tag v3.0.1
git push origin v3.0.1

If you go to GitHub and go to the Releases tab you will see the newly created tag. Now you are ready to create the release. Click on Draft a new release to bring up the form to create a new release.


Fig. 10.29 Creating a new release.

Now you can enter information about the release. Set the Tag version to v3.0.1, the Release title to v3.0.1 and copy and paste the description from the 3.0.0 release into the description, changing the link to the release notes appropriately. At this point you can go to the bottom of the window and click on Publish release.


Fig. 10.30 Entering information about the release.

Your newly created release will now appear.


Fig. 10.31 The newly created release.

10.3. Updating the Spack package.py file

Once a new VisIt release is actually available as a release, the Spack package.py file for building VisIt with Spack should be reviewed for any changes needed to build this release. Generally, this work should be put in a pull request to Spack’s develop branch. We think Spack is being released often enough that changes pushed to their develop will make it into a public release less than a few months later. If earlier public availability of this release of VisIt with Spack is needed, then have a look at Spack’s project boards to find a suitable upcomming minor release and consider pushing it there. Be aware, however, that if any of the changes made result in changes to how VisIt conrcretizes in Spack, it may be required to be delayed to a major release of Spack.

10.4. Deleting a release

If you mess up the tag or the release you can delete the tag using git commands.

git tag -d v3.0.1
git push origin :refs/tags/v3.0.1

You can then remove the release at GitHub. The release will change to a draft release because the tag no longer exists. Go ahead and click on the release to bring up the draft release.


Fig. 10.32 Selecting the draft release corresponding to the deleted tag.

Click on Delete to delete the release.


Fig. 10.33 Deleting the draft release corresponding to the deleted tag.