For better documentation of release day work, I'm filing this step as well this time, might also be a good idea in the future. As soon as the website is live with the new release, the announcement for it should be put up on the blog and sent to the newsgroups as well as the announce list.
One more thing to do along with those, when the website has the release, is to update the /topic in #seamonkey with the release.
In this case, where we are just repeating the existing announcement with a different version number, we can copy old ones from the same channels, else we need to modify them with the correct info from the main copy in news.en.xml. SeaMonkey blog is done, stored as "unpublished" for the moment. For newsgroups and mailing lists, we convert it to plain text and pointing to the links after the announcement tests. I'm always looking up old announcements as templates. One message has: Newsgroups: mozilla.dev.apps.seamonkey,mozilla.support.seamonkey,mozilla.dev.planning,netscape.public.mozilla.seamonkey,mozilla.dev.l10n Followup-To: mozilla.support.seamonkey Another one goes via email to email@example.com and needs moderation from any list moderator (I can do it nowadays). I created both messages and staged them via "Send later".
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.