1 Instructions to create pretest or release tarballs.
2 -- originally written by Eli Zaretskii, amended by Francesco Potortì
4 For each step, check for possible errors.
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.
12 3. Set the version number (M-x load-file RET admin/admin.el RET, then
13 M-x set-version RET). For a release, add released change log
14 entries (M-x add-release-logs RET).
16 4. rm configure; make bootstrap
18 5. Commit configure, loaddefs.el, cus-load.el, finder-inf.el, README,
21 6. make-dist --snapshot. Check the contents of the new tar with
22 admin/diff-tar-files against an older tar file. Some old pretest
23 tarballs are kept under fencepost.gnu.org:~pot/emacs-pretest/.
25 7. xdelta delta emacs-OLD.tar.gz emacs-NEW.tar.gz emacs-OLD-NEW.xdelta
27 8. tar -zxf emacs-NEW.tar.gz; cd emacs-NEW
28 configure && make && make -n install
29 Use `script' or M-x compile to save the compilation log in
30 compile-NEW.log and compare it against an old one. The easiest way
31 to do that is to visit the old log in Emacs, change the version
32 number of the old Emacs to __, do the same with the new log and do
33 M-x ediff. Especially check that Info files aren't built.
35 9. cd EMACS_ROOT_DIR; cvs tag TAG
36 TAG is EMACS_PRETEST_XX_YY_ZZZ for a pretest. Don't know for a release.
38 10. admin/make-announcement OLD NEW
39 This creates an announcement for pretests. Don't know for a release.
41 11. rsync emacs-NEW.tar.gz emacs-OLD-NEW.xdelta compile-NEW.log \
42 emacs-new.announce alpha.gnu.org:/home/alpha/gnu/emacs/pretest/
44 12. Verify that after five minutes at most the files appear on
45 ftp://alpha.gnu.org/gnu/emacs/pretest/.
47 13. Let Richard Stallman know about the new pretest and tell him to
48 announce it using the announcement you prepared. Remind him to set
49 a Reply-to header to <emacs-pretest-bug@gnu.org>.