Release Process

Checklist

For rolling new Haraka releases:

• Start a N-week quiet period
• Update haraka-tld
• Draft a release on the releases page (Save draft)
• Create a PR with:
  • Updated Changes
  • Bumped version in package.json
  • Updated dependencies identified with grunt versioncheck
• For major version releases:
  • check for waiting PRs for that milestone version.
  • Grep the source for: Sunset v3, where 3 is the new major version.
• Update release date in Changes
• git tag v<release_number>; git push --tags - done by publishing the release
• npm publish
• Post Changes file on the draft release and publish the release
• update haraka's wikipedia page
• Email the mailing list
• Publish a blog post
• Edit the /topic on #haraka IRC channel

Automation

Most of these steps are currently manual. Documenting the process is the first step towards automating it. There are some related comments here.

Automation Ideas

• https://github.com/skywinder/github-changelog-generator
• GitHub Releases haraka