From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: Proposal for a 22.2/trunk development model (was: Syncing Gnus and Emacs repositories) Date: Sun, 01 Jul 2007 16:40:18 -0400 Message-ID: References: <6sps3z32ap.fsf@fencepost.gnu.org> <87tztbcue9.fsf@stupidchicken.com> <87lkemmrg4.fsf@stupidchicken.com> <18033.64249.816850.550250@kahikatea.snap.net.nz> <200706161422.l5GEMTJ5009556@oogie-boogie.ics.uci.edu> Reply-To: rms@gnu.org NNTP-Posting-Host: lo.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: sea.gmane.org 1183322715 7418 80.91.229.12 (1 Jul 2007 20:45:15 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 1 Jul 2007 20:45:15 +0000 (UTC) Cc: rgm@gnu.org, handa@m17n.org, nickrob@snap.net.nz, emacs-devel@gnu.org, monnier@iro.umontreal.ca, cyd@stupidchicken.com To: Dan Nicolaescu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jul 01 22:45:13 2007 connect(): Connection refused 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 1I56IB-0002zU-Na for ged-emacs-devel@m.gmane.org; Sun, 01 Jul 2007 22:45:11 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1I56IB-0008BS-4s for ged-emacs-devel@m.gmane.org; Sun, 01 Jul 2007 16:45:11 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1I56DW-00075O-3E for emacs-devel@gnu.org; Sun, 01 Jul 2007 16:40:22 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1I56DV-00074Q-9t for emacs-devel@gnu.org; Sun, 01 Jul 2007 16:40:21 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1I56DV-00074C-7E for emacs-devel@gnu.org; Sun, 01 Jul 2007 16:40:21 -0400 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1I56DU-0005Kd-UH for emacs-devel@gnu.org; Sun, 01 Jul 2007 16:40:21 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.60) (envelope-from ) id 1I56DS-0006cK-Pn; Sun, 01 Jul 2007 16:40:18 -0400 In-reply-to: <200706161422.l5GEMTJ5009556@oogie-boogie.ics.uci.edu> (message from Dan Nicolaescu on Sat, 16 Jun 2007 07:22:24 -0700) X-detected-kernel: Linux 2.6, seldom 2.4 (older, 4) 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:74150 Archived-At: Please forgive me for taking so long to respond to your message. Here is a proposal that would still achieve the same goal, with the added advantage that it would get us closer to a future 23.1 release at a higher speed: * open the trunk for any new development Now, during the summer, is a very good time to allow for more development to happen: a lot of people have more free time, we'd want them to use that time for emacs as much as possible. The trunk is open now for nearly all new development. For instance, I hope we will merge the multi-tty branch in a few days. The only exception is unicode-2, but that exception won't last long. I hope we will make a 22.2 release in a few weeks; after that, we could merge unicode-2 also. Now, turning to your suggestion: * ask for 2-3 (or more) volunteers that would: - backport all the changes that you'd consider important from trunk to the 22.x branch - develop fixes for bugs that only occur on the 22.x branch - analyze the reported 22.1 bugs and fix them or ask for help to fix them - ask you to stop all development on the trunk until some critical bug is fixed on the branch. You proposed this as a way to get the trunk open for new development by everyone else. It isn't needed for that purpose, but it would be useful for the sake of making the Emacs 22.2 release without delays. Actually it is just a matter of fixing the bugs that are reported. Would people like to volunteer for this?