Mercurial > emacs
view admin/make-tarball.txt @ 72203:eddf5f0ed3c9
Merge from gnus--rel--5.10
Patches applied:
* gnus--rel--5.10 (patch 121-122)
- Update from CVS
2006-07-28 Reiner Steib <Reiner.Steib@gmx.de>
* etc/GNUS-NEWS: Regenerate from Oort Gnus node in texi/gnus.texi using
texi/gnus-news.el of the trunk.
2006-07-28 Katsumi Yamaoka <yamaoka@jpl.org>
* lisp/gnus/nnheader.el (nnheader-insert-head): Make it work with Mac as well.
2006-07-27 Katsumi Yamaoka <yamaoka@jpl.org>
* lisp/gnus/nnheader.el (nnheader-insert-head): Make it work even if the file
uses CRLF for the line-break code.
2006-07-28 Katsumi Yamaoka <yamaoka@jpl.org>
* man/gnus.texi (Oort Gnus): Mention that the Lisp files are now installed
in .../site-lisp/gnus/ by default.
[ From gnus-news.texi in the trunk. ]
2006-07-27 Reiner Steib <Reiner.Steib@gmx.de>
* man/gnus.texi (MIME Commands): Additions for yEnc.
Revision: emacs@sv.gnu.org/emacs--devo--0--patch-375
author | Miles Bader <miles@gnu.org> |
---|---|
date | Mon, 31 Jul 2006 09:40:13 +0000 |
parents | 9b288e127305 |
children | 52051ccbb0d0 e6bf73e43cf4 |
line wrap: on
line source
Instructions to create pretest or release tarballs. -- originally written by Gerd Moellmann, amended by Francesco Potort́ with the initial help of Eli Zaretskii For each step, check for possible errors. 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 necessary to check it out. 3. Regenerate Emacs' AUTHORS file (M-x load-file RET lisp/emacs-lisp/authors.el RET, then M-x authors RET, then save the *Authors* buffer). This may require fixing syntactically incorrect ChangeLog entries beforehand. 4. Set the version number (M-x load-file RET admin/admin.el RET, then M-x set-version RET). For a release, add released change log entries (M-x add-release-logs RET). 5. rm configure; make bootstrap 6. Commit configure, README, AUTHORS, lisp/cus-load.el, lisp/finder-inf.el, lisp/version.el, man/emacs.texi, lispref/elisp.texi. Copy lisp/loaddefs.el to lisp/ldefs-boot.el and commit lisp/ldefs-boot.el. 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 tarballs are kept under fencepost.gnu.org:~pot/emacs-pretest/, while old emacs tarballs are at <ftp://ftp.gnu.org/pub/gnu/emacs/>. 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 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 TAG is EMACS_PRETEST_XX_YY_ZZZ for a pretest, EMACS_XX_YY for a release. 11. admin/make-announcement OLD NEW This creates an announcement for pretests. OLD is the version used 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. 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 <ftp-upload@gnu.org> 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. 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. 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>. For a release, Richard should prepare the announcement himself, possibly starting from a previous announcment. # arch-tag: c23c771f-ca26-4584-8a04-50ecf0989390