diff options
Diffstat (limited to 'admin/make-tarball.txt')
| -rw-r--r-- | admin/make-tarball.txt | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/admin/make-tarball.txt b/admin/make-tarball.txt index e5c77172c9f..5822f666db4 100644 --- a/admin/make-tarball.txt +++ b/admin/make-tarball.txt @@ -18,7 +18,7 @@ Steps to take before starting on the first pretest in any release sequence: when preparing the first pretest for a major Emacs release.) Commit cus-edit.el if changed. -3. Remove any old pretests from ftp://alpha.gnu.org/gnu/emacs/pretest. +3. Remove any old pretests from https://alpha.gnu.org/gnu/emacs/pretest. You can use 'gnupload --delete' (see below for more gnupload details). General steps (for each step, check for possible errors): @@ -101,8 +101,8 @@ General steps (for each step, check for possible errors): Check the contents of the new tar with admin/diff-tar-files against the previous release (if this is the first pretest) or the previous pretest. If you did not make the previous pretest - yourself, find it at <ftp://alpha.gnu.org/gnu/emacs/pretest>. - Releases are of course at <ftp://ftp.gnu.org/pub/gnu/emacs/>. + yourself, find it at <https://alpha.gnu.org/gnu/emacs/pretest>. + Releases are of course at <https://ftp.gnu.org/pub/gnu/emacs/>. If this is the first pretest of a major release, just comparing with the previous release may overlook many new files. You can try @@ -130,9 +130,9 @@ General steps (for each step, check for possible errors): 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. For instructions, see - http://www.gnu.org/prep/maintain/html_node/Automated-Upload-Registration.html + https://www.gnu.org/prep/maintain/html_node/Automated-Upload-Registration.html The simplest method to upload is to use the gnulib - <http://www.gnu.org/s/gnulib/> script "build-aux/gnupload": + <https://www.gnu.org/s/gnulib/> script "build-aux/gnupload": For a pretest: gnupload [--user your@gpg.key.email] --to alpha.gnu.org:emacs/pretest \ @@ -161,11 +161,11 @@ General steps (for each step, check for possible errors): FILE.sig, FILE.directive.asc. For a release, place the files in the /incoming/ftp directory. For a pretest, place the files in /incoming/alpha instead, so that - they appear on ftp://alpha.gnu.org/. + they appear on https://alpha.gnu.org/. 10. After five minutes, verify that the files are visible at - ftp://alpha.gnu.org/gnu/emacs/pretest/ for a pretest, or - ftp://ftp.gnu.org/gnu/emacs/ for a release. + https://alpha.gnu.org/gnu/emacs/pretest/ for a pretest, or + https://ftp.gnu.org/gnu/emacs/ for a release. Download them and check the signatures. Check they build. @@ -185,7 +185,7 @@ UPDATING THE EMACS WEB PAGES AFTER A RELEASE As soon as possible after a release, the Emacs web pages should be updated. Anyone with write access to the Emacs code repository can do this. -For instructions, see <http://savannah.gnu.org/cvs/?group=emacs>. +For instructions, see <https://savannah.gnu.org/cvs/?group=emacs>. Changes go live more or less as soon as they are committed. The pages to update are: @@ -215,5 +215,5 @@ Add compressed copies of the main info pages from the tarfile to manual/info/. Update the refcards/pdf/ and ps/ directories, and also refcards/emacs-refcards.tar.gz (use make -C etc/refcards pdf ps dist). -Browsing <http://web.cvs.savannah.gnu.org/viewvc/?root=emacs> is one +Browsing <https://web.cvs.savannah.gnu.org/viewvc/?root=emacs> is one way to check for any files that still need updating. |