From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: Updating release version to 22.1 Date: Wed, 09 Feb 2005 11:45:41 +0100 Message-ID: References: <87vf92sqby.fsf@marant.org> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: sea.gmane.org 1107948815 29138 80.91.229.2 (9 Feb 2005 11:33:35 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 9 Feb 2005 11:33:35 +0000 (UTC) Cc: miles@gnu.org, snogglethorpe@gmail.com, rms@gnu.org, =?iso-8859-1?q?J=E9r=F4me_Marant?= , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Feb 09 12:33:34 2005 Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1Cyq5S-0001w1-HH for ged-emacs-devel@m.gmane.org; Wed, 09 Feb 2005 12:32:50 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1CyqJy-0006LZ-Jq for ged-emacs-devel@m.gmane.org; Wed, 09 Feb 2005 06:47:50 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Cyq3D-0002jK-J3 for emacs-devel@gnu.org; Wed, 09 Feb 2005 06:30:32 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Cyq3B-0002ik-0T for emacs-devel@gnu.org; Wed, 09 Feb 2005 06:30:29 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Cyq3A-0002SI-Cz for emacs-devel@gnu.org; Wed, 09 Feb 2005 06:30:28 -0500 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CypLy-0004M2-IG for emacs-devel@gnu.org; Wed, 09 Feb 2005 05:45:50 -0500 Original-Received: from localhost ([127.0.0.1] helo=lola.goethe.zz) by fencepost.gnu.org with esmtp (Exim 4.34) id 1CypIP-0004of-Ha; Wed, 09 Feb 2005 05:42:09 -0500 Original-To: storm@cua.dk (Kim F. Storm) In-Reply-To: (Kim F. Storm's message of "Wed, 09 Feb 2005 09:30:42 +0100") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/21.3.50 (gnu/linux) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org X-MailScanner-To: ged-emacs-devel@m.gmane.org Xref: main.gmane.org gmane.emacs.devel:33129 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:33129 storm@cua.dk (Kim F. Storm) writes: > Miles Bader writes: > >> On Wed, 09 Feb 2005 01:17:30 +0100, Kim F. Storm wrote: >>> > On Tue, 08 Feb 2005 22:18:41 +0100, J=E9r=F4me Marant wrote: >>> >> What's the rational for not using 22.0.x for development versions? >>> >> It would be so much simpler ... >>>=20 >>> Because it - IMO - is confusing. >> >> What, compared to all the other bizarro schemes being suggested here >> ("hey I know, let's make pre-releases _blue_, and real releases >> _green_!")? You've got to be kidding... please say you're kidding... > > Not really! > > The problem with our _current_ scheme is that even though we seem to > want to postpone the decision about exactly what number the next > release gets, it is recorded _NUMEROUS_ places all over the sources > and other files (in total, I had to change 21.4 to 22.1 in more than > 500 places). That is not counting the 8000+ web pages containing Emacs-21.4... > I don't want us to get into that mess again -- so I want a scheme > where the next release number is _fixed_ from the start. This assumes that most version numbers in the text can stay ("will be available with version xxx" is a good candidate). That will still need to cater for "the current version is xxx", but maybe _those_ can partly be autogenerated with CVS keywords, depending on the kind of text? In AUCTeX, we have something like (eval-and-compile (defconst AUCTeX-version (eval-when-compile (let ((name "$Name: $") (rev "$Revision: 5.482 $")) (or (when (string-match "\\`[$]Name: *\\(release_\\)?\\([^ ]+\\) *[$]\\'" name) (setq name (match-string 2 name)) (while (string-match "_" name) (setq name (replace-match "." t t name))) name) (if (string-match "\\`[$]Revision: *\\([^ ]+\\) *[$]\\'" rev) (format "CVS-%s" (match-string 1 rev))) "unknown"))) "AUCTeX version. If not a regular release, CVS revision of `tex.el'.")) It's less than perfect, but at least it is something one can't forget. It also means that you need to export using the version tag when doing a release. --=20 David Kastrup, Kriemhildstr. 15, 44793 Bochum