From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Glenn Morris Newsgroups: gmane.emacs.devel Subject: Re: Pretest and branch on Friday June 19 Date: Sat, 13 Jun 2009 16:50:16 -0400 Message-ID: References: <87k53h10vx.fsf@cyd.mit.edu> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1244926265 27287 80.91.229.12 (13 Jun 2009 20:51:05 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 13 Jun 2009 20:51:05 +0000 (UTC) Cc: emacs-devel@gnu.org To: Chong Yidong Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jun 13 22:51:02 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1MFaBJ-0008H3-Ju for ged-emacs-devel@m.gmane.org; Sat, 13 Jun 2009 22:50:29 +0200 Original-Received: from localhost ([127.0.0.1]:49766 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MFaBJ-0006Bv-5L for ged-emacs-devel@m.gmane.org; Sat, 13 Jun 2009 16:50:29 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MFaBE-0006BU-0k for emacs-devel@gnu.org; Sat, 13 Jun 2009 16:50:24 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MFaB9-00068f-FM for emacs-devel@gnu.org; Sat, 13 Jun 2009 16:50:23 -0400 Original-Received: from [199.232.76.173] (port=52745 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MFaB9-00068F-8m for emacs-devel@gnu.org; Sat, 13 Jun 2009 16:50:19 -0400 Original-Received: from fencepost.gnu.org ([140.186.70.10]:42166) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MFaB8-0001yC-VX for emacs-devel@gnu.org; Sat, 13 Jun 2009 16:50:19 -0400 Original-Received: from rgm by fencepost.gnu.org with local (Exim 4.67) (envelope-from ) id 1MFaB7-000826-3b; Sat, 13 Jun 2009 16:50:17 -0400 X-Spook: cryptanalysis afsatcom Crowell interception World Trade X-Ran: (~I~La|a\j[9v~$<;eEb4Y3K^GwU&p85I7`_@'TBhNIQYYQEhhW?`JvIUB{N8HucJ*sxmj X-Hue: magenta X-Attribution: GM User-Agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) 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 Xref: news.gmane.org gmane.emacs.devel:111496 Archived-At: Chong Yidong wrote: > I'm not certain what version number to assign the trunk after branching. > I'm inclined to use 23.1.50, which assumes we'll use the trunk for > developing 23.2. I think it depends on what Emacs version numbers are supposed to mean. If a bump in the major version means "major new feature(s)" (eg unicode, multi-tty), then yes, do what you said. Personally, I like the convention Emacs 22 fell into: Going from 22.1 to 22.2, only bug fixes or entirely self-contained new features (eg a brand new package "foo-mode.el") were allowed. This meant 22.2 could never be worse than 22.1 in any aspect. I'd like the same thing to happen again for the 23 series. I don't see it as a problem if there is only ever a 23.2, with very few (bug-fix or entirely new packages) changes over 23.1, and if 24.1 comes along relatively quickly with no "huge" changes. Version numbers are cheap. If the trunk is used for 23.2, then I feel like I'd have to hold off making non-bugfix changes to any existing feature, in case of inadvertent breakage. The feature freeze is already almost a year old, and it's rather disheartening not to be able to do development. So I think I'd prefer "24.0.50".