From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: "Stefan Monnier" Newsgroups: gmane.emacs.devel Subject: Re: please consider emacs-unicode for pervasive changes Date: Fri, 19 Jul 2002 13:44:53 -0400 Sender: emacs-devel-admin@gnu.org Message-ID: <200207191744.g6JHisp16756@rum.cs.yale.edu> References: <200207181644.g6IGiuv11955@rum.cs.yale.edu> <200207191653.g6JGrpV26904@aztec.santafe.edu> NNTP-Posting-Host: localhost.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1027100752 19745 127.0.0.1 (19 Jul 2002 17:45:52 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Fri, 19 Jul 2002 17:45:52 +0000 (UTC) Cc: monnier+gnu/emacs@rum.cs.yale.edu, d.love@dl.ac.uk, emacs-devel@gnu.org Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 17Vbp9-00058M-00 for ; Fri, 19 Jul 2002 19:45:51 +0200 Original-Received: from fencepost.gnu.org ([199.232.76.164]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 17Vc1d-0002xf-00 for ; Fri, 19 Jul 2002 19:58:45 +0200 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.35 #1 (Debian)) id 17Vbog-0005dm-00; Fri, 19 Jul 2002 13:45:22 -0400 Original-Received: from rum.cs.yale.edu ([128.36.229.169]) by fencepost.gnu.org with esmtp (Exim 3.35 #1 (Debian)) id 17VboF-0005d3-00; Fri, 19 Jul 2002 13:44:55 -0400 Original-Received: (from monnier@localhost) by rum.cs.yale.edu (8.11.6/8.11.6) id g6JHisp16756; Fri, 19 Jul 2002 13:44:54 -0400 X-Mailer: exmh version 2.4 06/23/2000 with nmh-1.0.4 Original-To: Richard Stallman 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:5913 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:5913 > - feature freeze on the trunk. > - create a branch for Emacs_21_4 where we can commit bug-fixes during > the subsequent debugging+pretest+maintenance period. > - merge the emacs-unicode changes onto the trunk. > > This is unacceptable unless the emacs-unicode changes are almost ready > for real installation. I'm not sure I understand why. The three steps don't need to all take place at the very same time. Furthermore, during the debugging+pretest phase of Emacs-21.4 I expect that we should concentrate on debugging rather than new features so the trunk should most mostly quiet, which leaves more time for merging emacs-unicode. Finally, I agree that the changes should be "ready for installation", but that doesn't mean "100% completed". It just means that the main parts are done and working modulo bugs. The trunk is where the main activity should take place, so as soon as emacs-unicode is stable enough for other people (even if uninterested in unicode) to hack on, it should be merged. > If they are almost ready, then rather than > doing this, we may want to merge them into the trunk now and include > them in the next release. I hope that the work can be split enough that there's a "long time" between "ready for use" and "feature complete ready for release". Also I'd rather not delay the release of 21.4. > Basically, it's either in or out. Nice truism, Richard ;-) Stefan