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: 11 Apr 2004 13:04:41 +0200 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <8765cwkejr.fsf@mail.jurta.org> <200404071157.UAA25094@etlken.m17n.org> <200404071312.WAA25268@etlken.m17n.org> <87zn9nqras.fsf@emacswiki.org> <200404080203.LAA26847@etlken.m17n.org> <87u0zufp7t.fsf-monnier+emacs@alfajor.local> <20040410000843.GC7497@fencepost> <200404110308.MAA06356@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 1081682078 5836 80.91.224.253 (11 Apr 2004 11:14:38 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 11 Apr 2004 11:14:38 +0000 (UTC) Cc: miles@gnu.org, emacs-devel@gnu.org, monnier@iro.umontreal.ca, rms@gnu.org, storm@cua.dk Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Sun Apr 11 13:14:31 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 1BCcv1-0005ZS-00 for ; Sun, 11 Apr 2004 13:14:31 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BCcv0-0005IA-00 for ; Sun, 11 Apr 2004 13:14:31 +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 1BCcpQ-0002OW-BQ for emacs-devel@quimby.gnus.org; Sun, 11 Apr 2004 07:08:44 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30) id 1BCcoc-0002G0-RZ for emacs-devel@gnu.org; Sun, 11 Apr 2004 07:07:54 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30) id 1BCcnx-00026W-KA for emacs-devel@gnu.org; Sun, 11 Apr 2004 07:07:44 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.30) id 1BCclf-0001ex-Rk for emacs-devel@gnu.org; Sun, 11 Apr 2004 07:04:51 -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 1BCclY-00048O-Lc; Sun, 11 Apr 2004 07:04:45 -0400 Original-To: Kenichi Handa In-Reply-To: <200404110308.MAA06356@etlken.m17n.org> Original-Lines: 44 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:21476 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:21476 Kenichi Handa writes: > In article , storm@cua.dk (Kim F. Storm) writes: > > >> I did a test merge of multi-tty with tiling, and there are > >> actually very few patch conflicts, though the RIF changes > >> probably do mean there are few semantic errors in the result. > >> > >> I'd love see the multi-tty changes go in -- not just because > >> it's a great feature (and it is), but because I like the code > >> cleanup. Compared to the current "everything global all the > >> time" code, it should make things a bit easier to understand, > >> which is no small thing given the confusingness of the redisplay > >> code. > > > Yes, I also look forward to the RIF cleanup from the multi-tty > > patch. I had plans to do this cleanup myself sometime, but Romain > > beat me to it. > > > It should definitely go in soon after 21.5 is branched from trunk. > > I don't object to it, but if it changes some internal interfaces, > I'd like to ask to merge it after emacs-unicode merge is done. At > least emacs-unicode doesn't change RIF. In my opinion, we should first merge the unicode branch into the trunk. Once unicode is merged, multi-tty can merge the current trunk. Once this is done, one can judge the respective stabilities. If it turns out that the unicode branch merge left us with a rather stable system on the trunk, we should aim for releasing 22.1 as fast as possible. This means that multi-tty should only be merged if its HEAD (after merge in of the trunk's HEAD) seems similarly stable. Since we can't just right now judge how the stability is affected with the combined branches, I would postpone the decision of when to merge multi-tty until we have the actual merge candidates. When in doubt, there is no harm in releasing 22.0, noticing afterwards that the multi-head branch leaves us with a quite stable Emacs, too, and release 22.1 soon after that. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum