Skip to content

Latest commit

 

History

History
24 lines (17 loc) · 1.07 KB

RELEASE_PROCESS.md

File metadata and controls

24 lines (17 loc) · 1.07 KB
Raw

Release process

Travis CI is used as a backbone to get releases going.

It's currently using a secure Github API OAuth token with public_repo permissions bound to https://github.com/syndbg .

Rules

  1. Releases are only created from master.
  2. master is meant to be stable, so before tagging and create a new release, make sure that the CI checks pass.
  3. Releases are GitHub releases.
  4. Releases are following semantic versioning.
  5. Releases are to be named in pattern of vX.Y.Z. The produced binary artifacts contain the vX.Y.Z in their names.
  6. Changelog must up-to-date with what's going to be released. Check CHANGELOG.

Flow

  1. Create a new GitHub release using https://github.com/sumup-oss/vaulted/releases/new
  2. Tag Version and Release Title are going to be in pattern of vX.Y.Z.
  3. Describe this release (content) is going to link the appropriate CHANGELOG entry.
  4. Wait for Travis CI to pass checks
  5. Wait for the produced artifacts to be uploaded at https://github.com/sumup-oss/vaulted/releases/tag/<vX.Y.Z>