Skip to content

Latest commit

 

History

History
21 lines (15 loc) · 962 Bytes

RELEASE_PROCESS.md

File metadata and controls

21 lines (15 loc) · 962 Bytes
Raw

Release process

Releases are done manually.

Automation may be introduced, but currently they're not that much of an issue.

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.
  7. Make sure to bump the version of goenv. Bumping the version of go-build is often omitted.

Flow

  1. Create a new GitHub release using https://github.com/syndbg/goenv
  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.