diff options
| -rw-r--r-- | admin/make-tarball.txt | 22 |
1 files changed, 15 insertions, 7 deletions
diff --git a/admin/make-tarball.txt b/admin/make-tarball.txt index e54cc1e899..59fa166521 100644 --- a/admin/make-tarball.txt +++ b/admin/make-tarball.txt @@ -15,12 +15,14 @@ For each step, check for possible errors. 4. rm configure; make bootstrap -5. Commit configure, loaddefs.el, cus-load.el, finder-inf.el, README, - emacs.texi. +5. Commit configure, README, lisp/loaddefs.el, lisp/cus-load.el, + lisp/finder-inf.el, lisp/version.el, man/emacs.texi. For a release, + also commit the ChangeLog files in all directories. 6. make-dist --snapshot. Check the contents of the new tar with admin/diff-tar-files against an older tar file. Some old pretest - tarballs are kept under fencepost.gnu.org:~pot/emacs-pretest/. + tarballs are kept under fencepost.gnu.org:~pot/emacs-pretest/, while + old emacs tarballs are at <ftp://ftp.gnu.org/pub/gnu/emacs/>. 7. xdelta delta emacs-OLD.tar.gz emacs-NEW.tar.gz emacs-OLD-NEW.xdelta @@ -33,17 +35,23 @@ For each step, check for possible errors. M-x ediff. Especially check that Info files aren't built. 9. cd EMACS_ROOT_DIR; cvs tag TAG - TAG is EMACS_PRETEST_XX_YY_ZZZ for a pretest. Don't know for a release. + TAG is EMACS_PRETEST_XX_YY_ZZZ for a pretest, EMACS_XX_YY for a + release. 10. admin/make-announcement OLD NEW - This creates an announcement for pretests. Don't know for a release. + This creates an announcement for pretests. OLD is the version used + to make deltas with respect to NEW. *release instructions missing* -11. rsync emacs-NEW.tar.gz emacs-OLD-NEW.xdelta compile-NEW.log \ - emacs-new.announce alpha.gnu.org:/home/alpha/gnu/emacs/pretest/ +11. For a pretest, do: + rsync -aP emacs-NEW.tar.gz emacs-OLD-NEW.xdelta compile-NEW.log \ + emacs-NEW.announce alpha.gnu.org:/home/alpha/gnu/emacs/pretest/ + *release instructions missing* 12. Verify that after five minutes at most the files appear on ftp://alpha.gnu.org/gnu/emacs/pretest/. + *release instructions missing* 13. Let Richard Stallman 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 <[email protected]>. + *release instructions missing* |