Let everyone know about the new release
After the Release has been made on GitHub, it’s time to let everyone know:
These notification emails should be sent using the new version of NeoMutt.
Our two mailing lists get sent slightly different version of the release announcement. First, tidy some of the Markdown.
*(that’s enough emphasis for email)
Mail the Developers:
Neomutt Developers <email@example.com>
Next, strip out the sections mentioning Code, Build, Source, Upstream.
Mail the Users:
Neomutt Users <firstname.lastname@example.org>
Directly notify the downstream packagers using their team discussion board:
They can also be notified by mentioning them in Issues or PRs.
Update IRC topic:
/msg chanserv op #neomutt flatcap /topic Version: YYYY-MM-DD | "Teaching an Old Dog New Tricks" - https://neomutt.org | Twitter: https://twitter.com/NeoMutt_Org | Mailing lists: http://mailman.neomutt.org/mailman/listinfo | Code of Conduct: https://neomutt.org/conduct /msg chanserv deop #neomutt flatcap
Cut’n’paste the GitHub announcement into the neomutt.github.io repo.
The file should be named
Give it a YAML header:
--- author: flatcap title: Release YYYY-MM-DD ---
Also, add a line to the Releases webpage:
Commit and push the change to GitHub.
git add _post git commit --all --message "NeoMutt YYYY-MM-DD" git push origin
Strip down the release message to the bare essentials and link to the current release:
After the release, send each of the new contributors a ‘Thank You’ message containing a link to the GitHub Release Notes.