Skip to content

Latest commit

 

History

History
7 lines (6 loc) · 441 Bytes

RELEASE.md

File metadata and controls

7 lines (6 loc) · 441 Bytes
Raw

Releasing Errbit

  1. Ensure a GitHub mileston exists and that it is populated with all the substantive changes since the previous milestone.
  2. Ensure the current milestone is complete and create a next mileston in GitHub.
  3. Update the Errbit::VERSION constant with a new git commit.
  4. Create and sign a git tag named v pointing to the release commit and push it to GitHub.
  5. Announce the new version on the mailing list.