admin/make-tarball.txt

   1 Instructions to create pretest or release tarballs.
   2 -- originally written by Eli Zaretskii, amended by Francesco Potortì
   3
   4 For each step, check for possible errors.
   5
   6 1.  cvs -q update -Pd
   7
   8 2.  Bootstrap to make 100% sure all elc files are up-to-date, and to
   9     make sure that the later tagged version will bootstrap, should it be
  10     necessary to check it out.
  11
  12 3.  Regenerate Emacs' AUTHORS file (M-x load-file RET
  13     lisp/emacs-lisp/authors.el RET, then M-x authors RET, then save
  14     the *Authors* buffer).  This may require fixing syntactically
  15     incorrect ChangeLog entries beforehand.
  16
  17 4.  Set the version number (M-x load-file RET admin/admin.el RET, then
  18     M-x set-version RET).  For a release, add released change log
  19     entries (M-x add-release-logs RET).
  20
  21 5.  rm configure; make bootstrap
  22
  23 6.  Commit configure, README, AUTHORS, lisp/loaddefs.el,
  24     lisp/cus-load.el, lisp/finder-inf.el, lisp/version.el,
  25     man/emacs.texi.  For a release, also commit the ChangeLog files in
  26     all directories.
  27
  28 7.  make-dist --snapshot.  Check the contents of the new tar with
  29     admin/diff-tar-files against an older tar file.  Some old pretest
  30     tarballs are kept under fencepost.gnu.org:~pot/emacs-pretest/, while
  31     old emacs tarballs are at <ftp://ftp.gnu.org/pub/gnu/emacs/>.
  32
  33 8.  xdelta delta emacs-OLD.tar.gz emacs-NEW.tar.gz emacs-OLD-NEW.xdelta
  34
  35 9.  tar -zxf emacs-NEW.tar.gz; cd emacs-NEW
  36     configure && make && make -n install
  37     Use `script' or M-x compile to save the compilation log in
  38     compile-NEW.log and compare it against an old one.  The easiest way
  39     to do that is to visit the old log in Emacs, change the version
  40     number of the old Emacs to __, do the same with the new log and do
  41     M-x ediff. Especially check that Info files aren't built.
  42
  43 10. cd EMACS_ROOT_DIR; cvs tag TAG
  44     TAG is EMACS_PRETEST_XX_YY_ZZZ for a pretest, EMACS_XX_YY for a
  45     release.
  46
  47 11. admin/make-announcement OLD NEW
  48     This creates an announcement for pretests.  OLD is the version used
  49     to make deltas with respect to NEW.  Anouncements for pretests need
  50     to be crafted by hand.  Use an older announcement to start with.
  51
  52 12. For the moment, put the tarballs on a public site and send a GPG
  53     signed email to <maintainers@gnu.org> with the URLs of the tarballs
  54     and their md5sum signatures.  As of 2003-10, the GNU maintainers are
  55     working on a better procedure.  For reference, here are the previous
  56     instructions, which are no more valid after the break-in of 2003-08:
  57      ====
  58     For a pretest, do:
  59     rsync -aP emacs-NEW.tar.gz emacs-OLD-NEW.xdelta compile-NEW.log \
  60     emacs-NEW.announce alpha.gnu.org:/home/alpha/gnu/emacs/pretest/.
  61     For a release, do:
  62     rsync -aP emacs-NEW.tar.gz emacs-OLD-NEW.xdelta \
  63     alpha.gnu.org:/home/ftp/gnu/emacs/.
  64
  65 13. Verify that the files are visible at
  66     ftp://alpha.gnu.org/gnu/emacs/pretest/ for a pretest, at
  67     ftp://ftp.gnu.org/gnu/emacs/ for a release.
  68
  69 14. For a pretest, let Richard Stallman know about the new pretest and
  70     tell him to announce it using the announcement you prepared.  Remind
  71     him to set a Reply-to header to <emacs-pretest-bug@gnu.org>.
  72     For a release, Richard should prepare the announcement himself,
  73     possibly starting from a previous announcment.
  74
  75 # arch-tag: c23c771f-ca26-4584-8a04-50ecf0989390