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.
(Ideally, with $user_agent set)
Our two mailing lists get sent slightly different version of the release announcement. First, tidy some of the Markdown.
** with * (that’s enough emphasis for email)\ (escaping backslashes)Mail the Developers: Neomutt Developers <neomutt-devel@neomutt.org>
Next, strip out the sections mentioning Code, Build, Source, Upstream.
Mail the Users: Neomutt Users <neomutt-users@neomutt.org>
Directly notify the downstream packagers using their team discussion board:
They can also be notified by mentioning them in Issues or PRs.
/cc @neomutt/downstream-packagersUpdate 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 _post/YYYY-MM-DD-release.md
Give it a YAML header:
---
author: flatcap
title: Release YYYY-MM-DD
---
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.
