Release Checklist

This page lists the steps to publish a new Conduit release.

Update Docs

• Create release notes entry for: http://software.llnl.gov/conduit/releases.html
• Build and update the docs on the gh-pages branch.
  • Include a copy of all docs for this release in a vX.Y.Z sub-dir (ex: v0.2.1 will appear at http://software.llnl.gov/conduit/v0.2.1/)

Close the Release Milestone on Github

• Make sure there are no outstanding issues and explicitly close the milestone

Publish the Release

• Start a release on github, name the release X.Y.Z (ex: 0.2.1)
• Add release notes (or shortened variant) to the release
• Recall Sphinx and Github use different markup, make sure to preview the release notes
• Tag master as vX.Y.Z (ex: v0.2.1)
• Don't forget the v prefix - the conduit spack package uses it in the fetch url

Update the Conduit Spack Package

• Download the release source conduit-X.Y.Z.tar.gz from github.
• Calc the md5 checksum for the release tarball:
• md5sum < conduit-X.Y.Z.tar.gz
• Add the version and checksum as a new entry to the conduit spack package.py
• Init a pull request to the spack develop branch to merge the conduit package.py update

Create a News Item for software.llnl.gov

• Create a new post for https://github.com/LLNL/llnl.github.io/tree/master/_posts
• Again, Sphinx and Github use different markup, see other posts for examples of the proper style
• Init a pull request to llnl.github.io master to merge and publish the post