Skip to content

Latest commit

 

History

History
25 lines (18 loc) · 1020 Bytes

RELEASING.md

File metadata and controls

25 lines (18 loc) · 1020 Bytes

Release Protocol

This document describes the steps for creating a new VAST release.

  1. Verify that the preconditions of a release are statisfied:
  • The current master HEAD builds successfully: Build Status
  • The documentation in README.md , the man page (doc/vast.1.md and doc/cli), and the docs website are up to date.
  1. Create a gpg-signed and annotated tag locally, and push it:
git tag -s "$(date '+%Y.%m.%d')" -m "$(date '+%Y.%m.%d')"
git push --follow-tags
  1. Draft a release on GitHub, and attach it to the tag.

  2. Publish the draft release. That will trigger a GitHub action run and build the project.

  3. Verify that the release CI action completed successfully. The GitHub action should upload all created artifacts and attach them to the published release.