mozilla

Heka release processΒΆ

This document contains a description of the steps taken to make a release of the Heka server.

  1. Review intended release branch for correct version number (in cmd/hekad/main.go, docs/source/conf.py, and CMakeLists.txt) and updated changelog (CHANGES.txt) and verify that the build succeeds and all tests pass.
  2. Tag verified commit on intended release branch with appropriate version tag.
  3. If this release is the highest released version number to date, the verified commit should be merged into the master branch.
  4. Bump version number (in cmd/hekad/main.go, docs/source/conf.py, and CMakeLists.txt) and add section for future release to changelog (CHANGES.txt). Commit “version bump” revision to the released version branch and push.
  5. Build all required binary packages.
  6. Create new github release (https://github.com/mozilla- services/heka/releases) and upload generated binaries.