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: It is time for a feature freeze (it is NOW or never). Date: 04 May 2004 10:17:49 +0200 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <20040504100343.846F.JMBARRANQUERO@wke.es> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1083658794 22402 80.91.224.253 (4 May 2004 08:19:54 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 4 May 2004 08:19:54 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Tue May 04 10:19:46 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 1BKv9W-0003h2-00 for ; Tue, 04 May 2004 10:19:46 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BKv9W-0002OH-00 for ; Tue, 04 May 2004 10:19:46 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.30) id 1BKv8I-0006QA-Ts for emacs-devel@quimby.gnus.org; Tue, 04 May 2004 04:18:30 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30) id 1BKv8D-0006Pe-Jo for emacs-devel@gnu.org; Tue, 04 May 2004 04:18:25 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30) id 1BKv7g-0006HP-6i for emacs-devel@gnu.org; Tue, 04 May 2004 04:18:24 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.30) id 1BKv7f-0006HJ-V0 for emacs-devel@gnu.org; Tue, 04 May 2004 04:17:51 -0400 Original-Received: from fencepost.gnu.org ([127.0.0.1] helo=lola.goethe.zz) by fencepost.gnu.org with esmtp (Exim 4.24) id 1BKv7f-00064z-B3; Tue, 04 May 2004 04:17:51 -0400 Original-To: Juanma Barranquero In-Reply-To: <20040504100343.846F.JMBARRANQUERO@wke.es> Original-Lines: 35 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.4 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:22689 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:22689 Juanma Barranquero writes: > On 04 May 2004 09:14:26 +0200 > David Kastrup wrote: > > > So if we skip this bugfix release, let us also skip the number. > > I fully agree... > > > reserving 21.4 for a > > possible bug fix release in case something horrible turns up that > > needs immediate fixing during that time might not do harm. > > ...but this doesn't seem very sensible. Getting out a 21.5 and > *afterwards* a bug-fix 21.4 would be confusing, to say the least. No, no. The 21.4 was supposed to be reserved as a bug fix release to 21.3. Once 21.5 is out, 21.4 should not appear: then people have to jump the gun and help us get the bug out from 21.5 instead. I just wanted to take 21.4 as a reserve when we know that 21.5 can't be out soon, but we would very much need a particular bug fix to 21.3 to be out before that. > But in fact I think that if something horrible happens after 21.5, > the thing to do would be to fix it as quickly as posible, and > meanwhile recommend users to stand with the stable 21.3. Right. I was talking about reserving 21.4 for _before_ 21.5 is released. Once we consider the trunk stable enough for an 21.5 release to be imminent, expending work on an in-between bug fix release would be inappropriate. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum