# HG changeset patch # User Francesco Potort # Date 1107729151 0 # Node ID 6af50633a8f1e815160f1a6ba0d439c5c6520977 # Parent a2314da923ec5172fd8cff1fb78a5ff60f46a451 ftp upload procedure finally described diff -r a2314da923ec -r 6af50633a8f1 admin/make-tarball.txt --- a/admin/make-tarball.txt Sun Feb 06 16:48:59 2005 +0000 +++ b/admin/make-tarball.txt Sun Feb 06 22:32:31 2005 +0000 @@ -4,7 +4,7 @@ For each step, check for possible errors. -1. cvs -q update -Pd +1. cvs -q update -Pd 2. Bootstrap to make 100% sure all elc files are up-to-date, and to make sure that the later tagged version will bootstrap, should it be @@ -19,51 +19,52 @@ M-x set-version RET). For a release, add released change log entries (M-x add-release-logs RET). -5. rm configure; make bootstrap +5. rm configure; make bootstrap 6. Commit configure, README, AUTHORS, 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. -7. make-dist --snapshot. Check the contents of the new tar with - admin/diff-tar-files against an older tar file. Some old pretest +7. 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/, while old emacs tarballs are at . -8. xdelta delta emacs-OLD.tar.gz emacs-NEW.tar.gz emacs-OLD-NEW.xdelta +8. xdelta delta emacs-OLD.tar.gz emacs-NEW.tar.gz emacs-OLD-NEW.xdelta -9. tar -zxf emacs-NEW.tar.gz; cd emacs-NEW - configure && make && make -n install +9. tar -zxf emacs-NEW.tar.gz; cd emacs-NEW + configure && make && make -n install Use `script' or M-x compile to save the compilation log in compile-NEW.log and compare it against an old one. The easiest way to do that is to visit the old log in Emacs, change the version number of the old Emacs to __, do the same with the new log and do M-x ediff. Especially check that Info files aren't built. -10. cd EMACS_ROOT_DIR; cvs tag TAG +10. cd EMACS_ROOT_DIR; cvs tag TAG TAG is EMACS_PRETEST_XX_YY_ZZZ for a pretest, EMACS_XX_YY for a release. -11. admin/make-announcement OLD NEW +11. admin/make-announcement OLD NEW This creates an announcement for pretests. OLD is the version used - to make deltas with respect to NEW. Anouncements for pretests need - to be crafted by hand. Use an older announcement to start with. + to make deltas with respect to NEW. Announcements for releases need + to be crafted by hand. Use an older announcement to start with: + look in ssh://fencepost.gnu.org/~pot/emacs-tarballs/. -12. For the moment, put the tarballs on a public site and send a GPG - signed email to with the URLs of the tarballs - and their md5sum signatures. As of 2003-10, the GNU maintainers are - working on a better procedure. For reference, here are the previous - instructions, which are no more valid after the break-in of 2003-08: - ==== - 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/. - For a release, do: - rsync -aP emacs-NEW.tar.gz emacs-OLD-NEW.xdelta \ - alpha.gnu.org:/home/ftp/gnu/emacs/. +12. Now you should upload the files to the GNU ftp server. In order to + do that, you must be registered as an Emacs maintainer and have your + GPG key acknowledged by the ftp people. Mail + for instructions. Once you are there, for each file FILE to be + released, create a detached GPG binary signature and a clearsigned + directive file like this: + gpg -b FILE + echo directory: emacs/pretest > FILE.directive (for a pretest) + echo directory: emacs > FILE.directive (for a release) + gpg --clearsign FILE.directive + Upload by anonymous ftp to ftp://ftp-upload.gnu.org/incoming/ftp/ + the files FILE, FILE.sig, FILE.directive.asc -13. Verify that the files are visible at +13. After five minutes, verify that the files are visible at ftp://alpha.gnu.org/gnu/emacs/pretest/ for a pretest, at ftp://ftp.gnu.org/gnu/emacs/ for a release.