From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Kenichi Handa Newsgroups: gmane.emacs.devel Subject: Re: It is time for a feature freeze (it is NOW or never). Date: Thu, 8 Apr 2004 11:03:49 +0900 (JST) Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <200404080203.LAA26847@etlken.m17n.org> 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> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII X-Trace: sea.gmane.org 1081389995 25241 80.91.224.253 (8 Apr 2004 02:06:35 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 8 Apr 2004 02:06:35 +0000 (UTC) Cc: rms@gnu.org, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Thu Apr 08 04:06:22 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 1BBOvu-0003MH-00 for ; Thu, 08 Apr 2004 04:06:22 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BBOvu-0004Ti-00 for ; Thu, 08 Apr 2004 04:06:22 +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 1BBOux-0000Pn-Mh for emacs-devel@quimby.gnus.org; Wed, 07 Apr 2004 22:05:23 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30) id 1BBOua-0000OV-9j for emacs-devel@gnu.org; Wed, 07 Apr 2004 22:05:00 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30) id 1BBOu4-0000En-CG for emacs-devel@gnu.org; Wed, 07 Apr 2004 22:04:59 -0400 Original-Received: from [192.47.44.130] (helo=tsukuba.m17n.org) by monty-python.gnu.org with esmtp (Exim 4.30) id 1BBOtX-000051-GF; Wed, 07 Apr 2004 22:03:55 -0400 Original-Received: from fs.m17n.org (fs.m17n.org [192.47.44.2]) by tsukuba.m17n.org (8.11.6p2/8.11.6) with ESMTP id i3823n827731; Thu, 8 Apr 2004 11:03:49 +0900 (JST) Original-Received: from etlken.m17n.org (etlken.m17n.org [192.47.44.125]) by fs.m17n.org (8.11.6p2/8.11.6) with ESMTP id i3823n916080; Thu, 8 Apr 2004 11:03:49 +0900 (JST) Original-Received: (from handa@localhost) by etlken.m17n.org (8.8.8+Sun/3.7W-2001040620) id LAA26847; Thu, 8 Apr 2004 11:03:49 +0900 (JST) Original-To: storm@cua.dk In-reply-to: (storm@cua.dk) User-Agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/21.3 (sparc-sun-solaris2.6) MULE/5.0 (SAKAKI) 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:21333 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:21333 In article , storm@cua.dk (Kim F. Storm) writes: > I suggest that we make a complete feature freeze on HEAD for 21.4 NOW !!! I have thought that we are going to take the following schedule. (1) Release the current RC branch as 21.4. (2) Feature freeze on HEAD. (3) Merge HEAD into RC branch, and make it 21.4.50. (4) Merge Unicode branch into HEAD, and make it 22.0.0. (5) Start pretest of 21.5 based on RC. (6) Release RC branch as 21.5. ... (7) Feature freeze on HEAD (i.e. Unicode version) (8) Merge HEAD into RC branch, and make it 22.0.50. Do you intend to skip (1)? Perhaps, that will be better because we can avoid disappointing users who exepect new features in the release of this long delay. > If we don't do it now, and start merging unicode and bidi to HEAD, I > fear that a 22.1 release is at least 1 year further into the future -- > and that CVS HEAD will go through a phase of lesser stable code than > we have been used to for quite some time (I'm not judging the quality > of the code on those branches, it's just that it hasn't been tested to > the same extent as HEAD, so we should expect problems). I agree. But, I think bug-fixing work for 21.5 (or 21.4) must be done on RC branch so that (4) can be done promptly and we can have more users of Unicode version, which boosts the release of 22.1. --- Ken'ichi HANDA handa@m17n.org