-12. For a pretest, announce it on emacs-devel and info-gnu-emacs@gnu.org.
- For a release, also announce it on info-gnu@gnu.org. (Probably
- bcc the info- addresses to make it less likely that people will
- followup on those lists.)
-
-13. For a release, update the Emacs homepage in the web repository.
- Also add the new NEWS file as NEWS.xx.y.
- Maybe regenerate the html manuals, update the FAQ, etc, etc.
+11. Send an announcement to: emacs-devel, and bcc: info-gnu-emacs@gnu.org.
+ For a pretest, also bcc: platform-testers@gnu.org.
+ (The reason for using bcc: is to make it less likely that people
+ will followup on the wrong list.)
+ See the info-gnu-emacs mailing list archives for the form
+ of past announcements. The first pretest announcement, and the
+ release announcement, should have more detail.
+
+12. For a release, update the Emacs homepage in the web repository.
+ Also update history.html, and add the new NEWS file as NEWS.xx.y.
+ Regenerate the html manuals (use make-manuals from admin.el).
+ If there are new manuals, add appropriate index pages.