From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: Post-22.1 development? Date: Mon, 04 Jun 2007 21:31:48 +0200 Message-ID: <856463sehn.fsf@lola.goethe.zz> References: <878xb05ras.fsf@stupidchicken.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1180985519 5890 80.91.229.12 (4 Jun 2007 19:31:59 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 4 Jun 2007 19:31:59 +0000 (UTC) Cc: Chong Yidong , emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jun 04 21:31:58 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1HvIHW-0002iK-1S for ged-emacs-devel@m.gmane.org; Mon, 04 Jun 2007 21:31:58 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HvIHV-0000fE-DM for ged-emacs-devel@m.gmane.org; Mon, 04 Jun 2007 15:31:57 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HvIHR-0000cJ-Qu for emacs-devel@gnu.org; Mon, 04 Jun 2007 15:31:53 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HvIHR-0000an-3R for emacs-devel@gnu.org; Mon, 04 Jun 2007 15:31:53 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HvIHQ-0000aV-V2 for emacs-devel@gnu.org; Mon, 04 Jun 2007 15:31:52 -0400 Original-Received: from mail-in-03.arcor-online.net ([151.189.21.43]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1HvIHP-0002m7-IX; Mon, 04 Jun 2007 15:31:51 -0400 Original-Received: from mail-in-01-z2.arcor-online.net (mail-in-01-z2.arcor-online.net [151.189.8.13]) by mail-in-03.arcor-online.net (Postfix) with ESMTP id 9E396278FF6; Mon, 4 Jun 2007 21:31:49 +0200 (CEST) Original-Received: from mail-in-02.arcor-online.net (mail-in-02.arcor-online.net [151.189.21.42]) by mail-in-01-z2.arcor-online.net (Postfix) with ESMTP id 8B4C213D7A1; Mon, 4 Jun 2007 21:31:49 +0200 (CEST) Original-Received: from lola.goethe.zz (dslb-084-061-097-035.pools.arcor-ip.net [84.61.97.35]) by mail-in-02.arcor-online.net (Postfix) with ESMTP id 603C77FC6; Mon, 4 Jun 2007 21:31:49 +0200 (CEST) Original-Received: by lola.goethe.zz (Postfix, from userid 1002) id 6B9EB1C2FE53; Mon, 4 Jun 2007 21:31:48 +0200 (CEST) In-Reply-To: (Richard Stallman's message of "Mon\, 04 Jun 2007 12\:44\:09 -0400") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1.50 (gnu/linux) X-detected-kernel: Linux 2.4-2.6 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:72224 Archived-At: Richard Stallman writes: > In a recent email, Stefan suggested that we should not restrict 22.x > development to bugfixes, but also include new features if the new > features are not too invasive. Do people agree with this approach? > > We can put in a limited set of new features, but only if they > are really important as well as safe. > > As for the trunk, should we begin merging the unicode branch in? > > Let's wait a couple of months. I think it will be easier to move > some changes selectively to the Emacs 22 branch if we have not > included unicode-2 in the trunk. As of now, any change in the trunk > would work in the branch. After unicode-2 is installed, many > changes will be done differently, and they won't work unchanged in > the Emacs 22 branch. I don't think this is a good plan, and here is why: EMACS_22_BASE is for work on Emacs 22.2 trunk is for work on Emacs 22.2 unicode-2 is for work on Emacs 23.1 This is clearly one branch too many (and I am not counting multi-tty yet). Since you yourself say that only important and safe changes should get into 22.2, I don't see the point in maintaining three branches. In particular, I don't see the point in keeping trunk stalled to mechanisms that won't work with Emacs 23.1. There have been a number of band-aid fixes to functions that were supposed to be replaced by proper code once the unicode-2 mechanisms are in use. There is no point in spending energy on stuff that is neither going to end up in Emacs 22.2 (since it is not important and safe enough), nor in Emacs 23.1 (since it fails to use the unicode-2 mechanisms). Please let us not waste time and energy on code that has no proper place in any future release. As long as no Emacs 23.1 mechanisms are involved, synching a unicode-2-empowered trunk's changes (if we want to) to EMACS_22_BASE will be easy. And where Emacs 23.1 mechanisms are involved, we don't actually want to figure out a parallel Emacs 22 mechanism, anyway. Not if it is not absolutely necessary. Merging unicode-2 to the trunk now rather than in a few months will help to keep the focus on the ongoing work for Emacs 23.1. We have stalled development for years in order to get a stable release out. We have put out a release, and created a branch for safe and important fixes to it. This is the time for the trunk to move on to Emacs 23.1. For Emacs 22.2, we have EMACS_22_BASE. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum