summaryrefslogtreecommitdiff
path: root/admin/make-tarball.txt
diff options
context:
space:
mode:
authorFrancesco Potortì <pot@gnu.org>2003-03-19 13:02:12 +0000
committerFrancesco Potortì <pot@gnu.org>2003-03-19 13:02:12 +0000
commit41a3c7b0279b3708a1cbd10803d94fa1d39bb972 (patch)
treed6435c2ec6dab3e3d5bdd7e9bb516d934a08b491 /admin/make-tarball.txt
parent229b28c432a6df8b02b8f6cb492ffd1bedb8db5c (diff)
downloademacs-41a3c7b0279b3708a1cbd10803d94fa1d39bb972.tar.gz
Release instructions added.
Diffstat (limited to 'admin/make-tarball.txt')
-rw-r--r--admin/make-tarball.txt26
1 files changed, 15 insertions, 11 deletions
diff --git a/admin/make-tarball.txt b/admin/make-tarball.txt
index d1189cf18ad..a9753f3fc49 100644
--- a/admin/make-tarball.txt
+++ b/admin/make-tarball.txt
@@ -40,18 +40,22 @@ For each step, check for possible errors.
10. admin/make-announcement OLD NEW
This creates an announcement for pretests. OLD is the version used
- to make deltas with respect to NEW. *release instructions missing*
+ to make deltas with respect to NEW. Anouncements for pretests need
+ to be crafted by hand. Use an older announcement to start with.
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 <emacs-pretest-bug@gnu.org>.
- *release instructions missing*
+ For a release, do:
+ rsync -aP emacs-NEW.tar.gz emacs-OLD-NEW.xdelta \
+ alpha.gnu.org:/home/ftp/gnu/emacs/.
+
+12. 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.
+
+13. For a pretest, 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 <emacs-pretest-bug@gnu.org>.
+ For a release, Richard should prepare the announcement himself,
+ possibly starting from a previous announcment.