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 16:37:25 +0200 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <87eks0654s.fsf@sno.mundell.ukfsn.org> <87n06bp4ng.fsf@sno.mundell.ukfsn.org> <8765cwkejr.fsf@mail.jurta.org> <200404071157.UAA25094@etlken.m17n.org> <200404071312.WAA25268@etlken.m17n.org> <87zn9nqras.fsf@emacswiki.org> <87hdvux5uz.fsf@orebokech.com> <87lll6v514.fsf@orebokech.com> <200404100109.KAA03816@etlken.m17n.org> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1083682187 12079 80.91.224.253 (4 May 2004 14:49:47 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 4 May 2004 14:49:47 +0000 (UTC) Cc: emacs-devel@gnu.org, rms@gnu.org, "Kim F. Storm" Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Tue May 04 16:49:38 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 1BL1Eo-0002yX-00 for ; Tue, 04 May 2004 16:49:38 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BL1Eo-0001rK-00 for ; Tue, 04 May 2004 16:49:38 +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 1BL17W-00056i-0K for emacs-devel@quimby.gnus.org; Tue, 04 May 2004 10:42:06 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30) id 1BL13p-0004Cm-LV for emacs-devel@gnu.org; Tue, 04 May 2004 10:38:17 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30) id 1BL138-0003sI-A3 for emacs-devel@gnu.org; Tue, 04 May 2004 10:38:05 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.30) id 1BL138-0003sE-19 for emacs-devel@gnu.org; Tue, 04 May 2004 10:37:34 -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 1BL131-0000rn-6g; Tue, 04 May 2004 10:37:27 -0400 Original-To: Stefan Monnier In-Reply-To: Original-Lines: 30 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:22714 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:22714 Stefan Monnier writes: > > I think that 21.4 has been mentioned frequently as probably another > > bug fix release, and 21.5 is "half-way" to 22.0. > > Huh? I think it's been much more mentioned as "the next big thing". > As in "will only be included in 21.4". That was once. And then there was a time where it was "21.4 will likely be another bug fix release". There was once talk to have another RC_1 branch release, before we decided to bite the bullet and go directly for a trunk release next. > And all the code currently refersw to 21.4. > > So I suggest we don't change anything for now (i.e. aim for 21.4). > If something bad happens we can always release a 21.4 bugfix and go through > the CVS code to fix the refs from 21.4 to 21.5. The problem is that I saw quite a few announcements of the "will be fixed/available in 21.4 or 21.5" by now. Since talk was made about another RC_1 release, people have amended the lines that once talked about the feature being in 21.2, 21.3 and 21.4 in succession. And if indeed people expect 21.4 to be the next great thing, releasing as 21.5 will do no harm. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum