From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: "Eli Zaretskii" Newsgroups: gmane.emacs.devel Subject: Emacs release procedure (Was: [h-e-w] Current word on binaries) Date: Sat, 21 Feb 2004 15:08:05 +0200 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <7105-Sat21Feb2004150804+0200-eliz@elta.co.il> References: <009901c3ec70$b3013940$6400a8c0@austin.rr.com> <7494-Sat14Feb2004140608+0200-eliz@elta.co.il> <40336BFC.3060908@gnu.org> <7704-Wed18Feb2004205431+0200-eliz@elta.co.il> Reply-To: Eli Zaretskii NNTP-Posting-Host: deer.gmane.org X-Trace: sea.gmane.org 1077369537 31808 80.91.224.253 (21 Feb 2004 13:18:57 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 21 Feb 2004 13:18:57 +0000 (UTC) Cc: Francesco Potorti` , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Sat Feb 21 14:18:35 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1AuX1f-0003jG-00 for ; Sat, 21 Feb 2004 14:18:35 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1AuX1f-00051n-00 for ; Sat, 21 Feb 2004 14:18:35 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.30) id 1AuWxp-000694-S8 for emacs-devel@quimby.gnus.org; Sat, 21 Feb 2004 08:14:37 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30) id 1AuWx8-00063B-1m for emacs-devel@gnu.org; Sat, 21 Feb 2004 08:13:54 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30) id 1AuWwZ-0005tU-4Q for emacs-devel@gnu.org; Sat, 21 Feb 2004 08:13:50 -0500 Original-Received: from [199.232.41.8] (helo=mx20.gnu.org) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.30) id 1AuWs2-0004gh-Rc; Sat, 21 Feb 2004 08:08:38 -0500 Original-Received: from [192.114.186.23] (helo=aragorn.inter.net.il) by mx20.gnu.org with esmtp (Exim 4.30) id 1AuWrv-00022h-7O; Sat, 21 Feb 2004 08:08:31 -0500 Original-Received: from zaretski ([80.230.147.104]) by aragorn.inter.net.il (MOS 3.4.4-GR) with ESMTP id CMV24192; Sat, 21 Feb 2004 15:08:27 +0200 (IST) Original-To: Harald Maier X-Mailer: emacs 21.3.50 (via feedmail 8 I) and Blat ver 1.8.9 In-reply-to: (message from Harald Maier on Thu, 19 Feb 2004 11:01:24 +0100) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:20095 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:20095 Here's a message sent in the past by Gerd Moellmann in which he summarized the procedure he used for making a pretest/release tarballs. Note that the specific versions and tags mentioned may need to be revised/modified for each specific release. Francesco, if you have any comments based on your experience of releasing v21.3, please do. One issue I remember from my experience is that there are directories present in the checked-out branch, such as lispref, which should not be in the tarball. They are there because they are present on the trunk and because the RC branch tag exists on those directories as well. The solution is either to remove the directories in your local sandbox, or (better) remove the branch tags from the files that are not supposed to exist on the branch, and use "cvs update -P" to let CVS prune empty directories when the tree is checked out. I'm cc'ing emacs-devel so that this procedure is archived and could be useful to future release managers. I started a new thread for the same reason. ------- Start of forwarded message ------- Subject: CVS tags Reply-To: gerd@gnu.org From: gerd.moellmann@t-online.de (Gerd Moellmann) Date: 24 Mar 2002 20:42:06 +0100 X-Sender: 520015515780-0001@t-dialin.net X-Status: A I see in the change logs that 21.2 has been released. Since there is no CVS tag for it, I wonder if I ever told that I did tag the releases and pretests to facilitate diffing etc., or if I did tell how I built the releases and pretests. In case it's useful, below is the exact procedure I followed. 1. cvs update 2. Run admin/build-configs to make sure Emacs builds in a number of frequently used configurations. Fix bugs. 3. 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. 4. Commit loaddefs.el, cus-load.el, finder-inf.el. 5. Run autoconf, commit configure. 5a. For a release, add released change log entries, and set the version number (M-x load-file RET admin/admin.el RET, then M-x add-release-logs RET, and M-x set-version RET). 6. make-dist --snapshot. Check the contents of the new tar with admin/diff-tar-files against an older tar file. 7. Make xdeltas 8. Untar the tar files made in 6, configure, build, install, saving the output of these phases with the script command. Check the output, esp. check that Info files aren't built. (Saving the output of the last release diffing helps spotting problems.) 9. `cvs tag EMACS_PRETEST_21_0_105' in the toplevel Emacs dir. (I used `EMACS_21_1' for the release tag.) 10. Increment version numbers in versions.el, README, emacs.texi. (See 5a). 11. Upload & announce. ------- End of forwarded message -------