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: 21.2.90 pretest, 21.3, 21.4... Date: 06 Nov 2002 13:40:18 +0100 Sender: emacs-devel-admin@gnu.org Message-ID: <5xbs52oor1.fsf@kfs2.cua.dk> References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1036584684 17896 80.91.224.249 (6 Nov 2002 12:11:24 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 6 Nov 2002 12:11:24 +0000 (UTC) Cc: Stefan Monnier , emacs-devel@gnu.org Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 189P1l-0004eR-00 for ; Wed, 06 Nov 2002 13:11:21 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 189PAF-0000Es-00 for ; Wed, 06 Nov 2002 13:20:07 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10) id 189P07-0003zo-00; Wed, 06 Nov 2002 07:09:39 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10) id 189OlA-0000kG-00 for emacs-devel@gnu.org; Wed, 06 Nov 2002 06:54:12 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10) id 189Ol4-0000jA-00 for emacs-devel@gnu.org; Wed, 06 Nov 2002 06:54:10 -0500 Original-Received: from mail.filanet.dk ([195.215.206.179]) by monty-python.gnu.org with esmtp (Exim 4.10) id 189OXm-0006sF-00 for emacs-devel@gnu.org; Wed, 06 Nov 2002 06:40:22 -0500 Original-Received: from kfs2.cua.dk.cua.dk (kfs2.local.filanet.dk [192.168.1.182]) by mail.filanet.dk (Postfix) with SMTP id 17DA07C017; Wed, 6 Nov 2002 11:40:21 +0000 (GMT) Original-To: Eli Zaretskii In-Reply-To: Original-Lines: 43 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 Errors-To: emacs-devel-admin@gnu.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.devel:9176 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:9176 Eli Zaretskii writes: > Feature freeze means there are _no_ new features until the thaw; Kai > suggested a finer control (allow some new features, but not others). IMO, a feature freeze on the trunk at the current state would be OK! There are now so many new features and fixes compared to 21.[1-3], that starting a pretest cycle for 21.4 from the trunk would be a _good thing_ to start getting all those new features tested (before we add even more features). Admittedly, it would halt "development" on the trunk for, say 2-3 months, but what's the purpose of such developments anyway if we (virtually) never make a release containing those new features? So I suggest that we announce a date (e.g. Dec 1st) for a trunk feature freeze and make the first pretest for 21.4 soon thereafter, with the goal of releasing 21.4 no later than Mar 1st, 2003! In my experience, the trunk has been very stable for a very long time [with a few hickups of course], so after the first few pretests, I would assume that the software would be stable enough for a release, or at least stable enough that we could make a 21_4 release branch for ironing out the final issues with the 21.4 release and remove the feature freeze on the trunk before Mar 1st (or whenever 21.4 will actually be ready). Are anyone of you aware of any significant stability (or redisplay) related bugs that we need to fix before 21.4 ? Are there any of the on-going tasks which *must be* completed before we release 21.4 ? I know we need some work on the manuals for the new features; maybe the goal of releasing 21.4 soon will also move our focus towards writing proper documentation for the new features (I know I still have a few pending tasks in that area). WDYT ?? -- Kim F. Storm http://www.cua.dk