-14. For a pretest, let Richard Stallman <rms@gnu.org> know about the new
- pretest and tell him to announce it using the announcement you prepared.
- Remind him to set a Reply-to header to <emacs-pretest-bug@gnu.org>.
-
-15. Shortly before the release, cut the branch with the following commands:
-
- cvs rtag EMACS_`NUMBER'_BASE
- cvs rtag -b EMACS_`NUMBER'_RC -r EMACS_`NUMBER'_BASE
-
-where `NUMBER' is the major version number of the release. This makes it
-easier to see what changes have been applied to the branch with:
-
- cvs diff -r EMACS_`NUMBER'_BASE -r EMACS_`NUMBER'_RC
-
-or merge changes back to the trunk with "cvs update -j", if necessary.
-
-After doing this, increase the version number on the trunk as per step 4.
-
-16. For a release, Richard should prepare the announcement himself,
- possibly starting from a previous announcment.
+13. For a pretest, announce it on emacs-devel and BCC the pretesters.
+ For a release, announce it on info-gnu@gnu.org,
+ info-gnu-emacs@gnu.org, and emacs-devel.