Skip to content

Latest commit

 

History

History
27 lines (22 loc) · 1.49 KB

RELEASING.md

File metadata and controls

27 lines (22 loc) · 1.49 KB

Releasing

  1. Communicate that a release is about to be released in the DaSCH Github Channel, so that no new Pull Requests are merged
  2. Create a new branch, e.g., releasing-vX.X.X
  3. Update the version number in CMakeLists.txt, manual/conf.py.
  4. Remove the (not released yet) text in the title of the release notes.
  5. Create a new page with the next version number including the (not released yet) text and add page to TOC.
  6. Update links in the new page to point to correct release tag and milestone.
  7. On Github - Create new milestone
  8. On Github - Move any open issues from current release milestone to the next release milestone and so on.
  9. On Github - Close current milestone.
  10. Push and merge PR to main.
  11. Travis CI will start a CI build for the new tag and publish artifacts to Docker Hub.
  12. On Github - Tag the commit with the version string, e.g., vX.X.X and create a release.
  13. On Github - Copy the release notes from the docs to the release.
  14. Publish documentation.

Under the Travis hood

Here is what happens in detail when Travis CI is building a git tagged commit. According to the .travis.yml file, the publish stage runs the following task:

  1. Credentials are read from the DOCKER_USER and DOCKER_PASS environment variables which are stored encrypted inside .travis.yml.
  2. The sipi docker image is build, tagged, and published.