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 01:17:30 +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 1107908275 10303 80.91.229.2 (9 Feb 2005 00:17:55 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 9 Feb 2005 00:17:55 +0000 (UTC) Cc: emacs-devel@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 01:17:54 2005 Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1CyfXl-0000WR-Fk for ged-emacs-devel@m.gmane.org; Wed, 09 Feb 2005 01:17:26 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Cyfm2-0006kb-JZ for ged-emacs-devel@m.gmane.org; Tue, 08 Feb 2005 19:32:06 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1CyflF-0006bD-OH for emacs-devel@gnu.org; Tue, 08 Feb 2005 19:31:17 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1CyflB-0006ZC-TF for emacs-devel@gnu.org; Tue, 08 Feb 2005 19:31:15 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1CyflB-0006Yv-PO for emacs-devel@gnu.org; Tue, 08 Feb 2005 19:31:13 -0500 Original-Received: from [195.41.46.235] (helo=pfepa.post.tele.dk) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CyfY0-0004Bu-HN; Tue, 08 Feb 2005 19:17:37 -0500 Original-Received: from kfs-l.imdomain.dk.cua.dk (0x503e2644.bynxx3.adsl-dhcp.tele.dk [80.62.38.68]) by pfepa.post.tele.dk (Postfix) with SMTP id 68E4447FE1C; Wed, 9 Feb 2005 01:17:31 +0100 (CET) Original-To: rms@gnu.org In-Reply-To: (Miles Bader's message of "Wed, 9 Feb 2005 07:38: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:33104 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:33104 Miles Bader writes: > On Tue, 08 Feb 2005 22:18:41 +0100, J=C3=A9r=C3=B4me Marant wrote: >> What's the rational for not using 22.0.x for development versions? >> It would be so much simpler ... Because it - IMO - is confusing. Right now (or two days ago) we had released 21.3 and were working on the trunk towards a release 21.4. But the version on the trunk is numbered 21.3.50 Typically, the user who built 21.3 has a version called 21.3.1 or 21.3.2 which is pretty close to 21.3.50 But if we could agree that we always release major versions from the trunk and each major release gets a new major number 22.1, 23.1, etc, I see no problem using 22.0.0, 23.0.0, etc as development versions, ans 22.0.1, 22.0.2, etc for the pretests. Bug fixes would be released from branches, and be named 22.2, 22.3, etc. Looking at past history, this wont cause major number inflation --=20 if lucky, we will release 30.1 in 2030 which isn't too bad :-) That is indeed a simple scheme which I would support. So Richard, if we could agree that major releasees from the trunk always gets a new major number, we will get a simple numbering scheme without the risk of accidentally using a "reserved" release number as you just did. It would be MUCH LESS HASSLE for future work if we implemented this scheme right away. I'll wait until tomorrow until I install my changes for 22.1 (or 22.0.0) --=20 Kim F. Storm http://www.cua.dk