Haraka
Haraka copied to clipboard
Release v3.0.0
RELEASE CHECKLIST
- [ ] Start a N-week quiet period
- [x] Update haraka-tld
- [x] Draft a release on the releases page (Save draft)
- Create a PR with:
- [x] Updated Changes
- [x] Bumped version in package.json
- 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.
- [x] Update release date in Changes
- [ ]
npm publish
- [x] Post
Changes
file on the draft release and publish the release - [ ] update haraka's wikipedia page
- [ ] Email the mailing list
- [ ] Publish a blog post
CHANGES
We're overdue for a release, and there's one more bug I'm aware of that needs tracking down before this one gets cut. I also think we're a bit guilty of sentimental versioning, and need hew closer to semver. This release has a couple breaking changes (noted with ! in the Changes) due to very long overdue updates to redis and generic-pool.
Also, I've been adding a bunch of automation to our release process. I've also created Haraka specific GitHub Workflows for new Haraka modules/plugins which are pretty nifty.