From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: storm@cua.dk (Kim F. Storm) Newsgroups: gmane.emacs.devel Subject: Re: Updating release version to 22.1 Date: Wed, 09 Feb 2005 12:23:08 +0100 Message-ID: References: <87vf92sqby.fsf@marant.org> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: sea.gmane.org 1107948908 29421 80.91.229.2 (9 Feb 2005 11:35:08 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 9 Feb 2005 11:35:08 +0000 (UTC) Cc: emacs-devel@gnu.org, rms@gnu.org, =?utf-8?q?J=C3=A9r=C3=B4me_Marant?= , miles@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Feb 09 12:35:07 2005 Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1Cyq7U-0002Ko-Lo for ged-emacs-devel@m.gmane.org; Wed, 09 Feb 2005 12:34:56 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1CyqM0-0006l5-LD for ged-emacs-devel@m.gmane.org; Wed, 09 Feb 2005 06:49:56 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1CyqDR-0004ee-8b for emacs-devel@gnu.org; Wed, 09 Feb 2005 06:41:05 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1CyqDO-0004d9-NU for emacs-devel@gnu.org; Wed, 09 Feb 2005 06:41:03 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1CyqDN-0004bw-N2 for emacs-devel@gnu.org; Wed, 09 Feb 2005 06:41:02 -0500 Original-Received: from [212.88.64.25] (helo=mail-relay.sonofon.dk) by monty-python.gnu.org with smtp (Exim 4.34) id 1Cypw2-0007rJ-CN for emacs-devel@gnu.org; Wed, 09 Feb 2005 06:23:06 -0500 Original-Received: (qmail 30931 invoked from network); 9 Feb 2005 11:23:05 -0000 Original-Received: from unknown (HELO kfs-l.imdomain.dk.cua.dk) (213.83.150.2) by 0 with SMTP; 9 Feb 2005 11:23:05 -0000 Original-To: snogglethorpe@gmail.com In-Reply-To: (Miles Bader's message of "Wed, 9 Feb 2005 17:41:37 +0900") 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:33130 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:33130 Miles Bader writes: >> 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. > > I have no idea what you're talking about. Which part of the sentense is difficult to understand? > > The problems caused by the current "mess" (21.4 released to mean > something else, 22.1 chosen for next release) would have happened > regardless of what scheme was chosen (including all of your wacky > ones), Stefan suggested 2.5 years ago to name the trunk version 22.1. Your response was: > From: Miles Bader > In-Reply-To: <200207021509.g62F9l617691@rum.cs.yale.edu> > Message-ID: <87n0taupfw.fsf@tc-1-100.kawasaki.gol.ne.jp> > Date: 03 Jul 2002 00:20:19 +0900 >=20=20 > "Stefan Monnier" writes: > > We could simply decide that RC versions will be 21.1, 21.2, 21.3, 21.4 > > and the next trunk version will be 22.1 (at which point it will be on i= ts > > own branch for 22.2, 22.3, 22.4, ...). >=20=20 > No, that would be silly. Emacs has a good history of changes in the > major version number really meaning that major changes were made; we > shouldn't screw that up unless it's for a very good reason (and I > haven't seen one presented yet). >=20=20 > -Miles Silly?=20=20 > because what occured is that an extra real release was added in > between the last real release and the designated next real release. Some of us saw it coming -- and you called us silly. And now I'm called wacky. Nice vocabulary, Miles. > No amount of futzing around with pre-release names would have changed > that. True -- that's not the main issue.=20=20 If you read my mail carefully, I'm discussing two issues: - preventing the current mess (always use MM.1 for trunk releases and MM.N (N > 1) for bug fixes from the RC_MM branch -- as Stefan wisely suggested back then. - finding a scheme for development and pretest naming that uses MM.1-something rather than _a completely different_ version number which MM.0-something is IMO. > The questions, as I understand it, are merely (1) how to call real > releases, and (2) how to call pre-releases. That's what I'm talking about! > > For the next release at least, it's been decided that (1) will be > "22.1"; what I understand J=C3=A9r=C3=B4me to have meant is that (2) in t= his > case should be "22.0.x", where x =3D 1, 2, 3, ... _IF_ we stick to 22.0-something for dev and pretest, I definitely prefer if we keep the current scheme of 22.0.50 and 22.0.90... rather than inventing something new. As I said, I'll use 22.0.50 when I change things later today. -- Kim F. Storm http://www.cua.dk