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: Reordering etc/NEWS Date: Thu, 10 May 2007 00:15:08 +0200 Message-ID: <853b25lk43.fsf@lola.goethe.zz> References: <2wmz0iriyj.fsf@fencepost.gnu.org> <87fy65k6eh.fsf@red-bean.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1178748958 3951 80.91.229.12 (9 May 2007 22:15:58 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 9 May 2007 22:15:58 +0000 (UTC) Cc: Eli Zaretskii , emacs-devel@gnu.org, rms@gnu.org, "Kim F. Storm" To: Karl Fogel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu May 10 00:15:56 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 1HluRv-0000wo-IF for ged-emacs-devel@m.gmane.org; Thu, 10 May 2007 00:15:56 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HluZ8-0000mL-N5 for ged-emacs-devel@m.gmane.org; Wed, 09 May 2007 18:23:22 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HluZ4-0000li-38 for emacs-devel@gnu.org; Wed, 09 May 2007 18:23:18 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HluYz-0000jN-Rn for emacs-devel@gnu.org; Wed, 09 May 2007 18:23:17 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HluYz-0000jK-La for emacs-devel@gnu.org; Wed, 09 May 2007 18:23:13 -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 1HluRH-0001f8-Rg; Wed, 09 May 2007 18:15:16 -0400 Original-Received: from mail-in-08-z2.arcor-online.net (mail-in-08-z2.arcor-online.net [151.189.8.20]) by mail-in-03.arcor-online.net (Postfix) with ESMTP id 9193F2CACA7; Thu, 10 May 2007 00:15:03 +0200 (CEST) Original-Received: from mail-in-03.arcor-online.net (mail-in-03.arcor-online.net [151.189.21.43]) by mail-in-08-z2.arcor-online.net (Postfix) with ESMTP id 837C12130DC; Thu, 10 May 2007 00:15:03 +0200 (CEST) Original-Received: from lola.goethe.zz (dslb-084-061-049-011.pools.arcor-ip.net [84.61.49.11]) by mail-in-03.arcor-online.net (Postfix) with ESMTP id 5E94E30A91D; Thu, 10 May 2007 00:15:03 +0200 (CEST) Original-Received: by lola.goethe.zz (Postfix, from userid 1002) id A059F1C27956; Thu, 10 May 2007 00:15:08 +0200 (CEST) In-Reply-To: <87fy65k6eh.fsf@red-bean.com> (Karl Fogel's message of "Wed\, 09 May 2007 14\:56\:38 -0700") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.98 (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:70718 Archived-At: Karl Fogel writes: > Why are we blocking new changes? Why not (say) have an open trunk, > and use a release branch to isolate the release from churn, like > other projects do? The one posting you have missed of importance is the one where Richard asked for volunteers that would consider taking over maintenance of Emacs once the release is out of the door. I have no idea what list of candidates, if any, has resulted from that. I also have no idea what candidates might have been struck from the list as the result of their way of voicing their concerns about the current process. I certainly hope the list is not empty. Richard has just announced that he plans on releasing Emacs 22.1 from the EMACS_BASE_22 branch. It is not clear to me what should right now happen on the trunk, though: should the branch merges of multitty and emacs-unicode-2 commence now, or later? Maybe Richard wants to leave the decision to whoever is going to end up as the maintainer of Emacs 23. And leave that decision until after 22.1 is released. I have seen that he is quite busy with travel and talk in Europe in the next few weeks. When I have a schedule like that, I know that I don't get pretty much any of the work done I plan to do alongside. In the light of that, I would consider it beneficial if Richard took a path before departure where we are not stalled waiting for him. This could either mean deciding what kind of merges may happen to what branch, or appointing someone to make these kind of decisions at least for some time. Whether or not he wants to let the release of 22.1 rest with somebody else is a different question. There is probably not much sense in that, since most candidates would probably just take EMACS_BASE_22 and just release it as-is. So he could, instead of passing the buck, equally well do this himself. I certainly hope that we can soon get to a state where work on Emacs 23 can commence, and also that we get to see a release soon. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum