; * admin/make-tarball.txt: Misc updates.

diff --git a/admin/make-tarball.txt b/admin/make-tarball.txt
index 8190e9edb8528bc2d3489e2c1751b209f7d4f887..d326282b9506f3b3c8082c18fa9a6ce7a8f540a1 100644 (file)
--- a/admin/make-tarball.txt
+++ b/admin/make-tarball.txt
@@ -63,6 +63,14 @@ General steps (for each step, check for possible errors):
     actual release.  If you need another release candidate, remember
     to adjust the ChangeLog entries.
 
+    If you need to change only a file(s) that cannot possibly affect
+    the build (README, ChangeLog, NEWS, etc.) then rather than doing
+    an entirely new build, it is better to unpack the existing
+    tarfile, modify the file(s), and tar it back up again.
+
+    Never replace an existing tarfile!  If you need to fix something,
+    always upload it with a different name.
+
 4.   autoreconf -i -I m4 --force
      make bootstrap
 
@@ -160,8 +168,38 @@ General steps (for each step, check for possible errors):
     of past announcements.  The first pretest announcement, and the
     release announcement, should have more detail.
 
-12. For a release, update the Emacs homepage emacs.html in the web repository.
-    Also update history.html, and add the new NEWS file as news/NEWS.xx.y.
-    Regenerate the html manuals (use make-manuals from admin.el).
-    If there are new manuals, add appropriate index pages.
-    Delete any old manual pages that are no longer present.
+12. After a release, update the Emacs pages as below.
+
+
+UPDATING THE EMACS WEB PAGES AFTER A RELEASE
+
+As soon as possible after a release, the Emacs web pages should be updated.
+Anyone with write access to the Emacs code repository can do this.
+For instructions, see <http://savannah.gnu.org/cvs/?group=emacs>.
+Changes go live more or less as soon as they are committed.
+
+The pages to update are:
+
+emacs.html (for a new major release, a more thorough update is needed)
+history.html
+add the new NEWS file as news/NEWS.xx.y
+
+Use M-x make-manuals from admin/admin.el to regenerate the html
+manuals in manual/.  If there are new manuals, add appropriate index
+pages in manual/ and add them to manual/index.html.  In the
+manual/html_node directory, delete any old manual pages that are no
+longer present.
+
+Tar up the generated html_node/emacs/ and elisp/ directories and update
+the files manual/elisp.html_node.tar.gz and emacs.html_node.tar.gz.
+
+Use M-x make-manuals-dist from from admin/admin.el to update the
+manual/texi/ tarfiles.
+
+Add compressed copies of the main info pages from the tarfile to manual/info/.
+
+Update the refcards/pdf/ and ps/ directories, and also
+refcards/emacs-refcards.tar.gz (use make -C etc/refcards pdf ps dist).
+
+Browsing <http://web.cvs.savannah.gnu.org/viewvc/?root=emacs> is one
+way to check for any files that still need updating.