From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Post-22.1 development? Date: Mon, 04 Jun 2007 22:35:08 +0300 Message-ID: References: <878xb05ras.fsf@stupidchicken.com> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: sea.gmane.org 1180985755 6795 80.91.229.12 (4 Jun 2007 19:35:55 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 4 Jun 2007 19:35:55 +0000 (UTC) Cc: emacs-devel@gnu.org To: Chong Yidong Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jun 04 21:35:50 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 1HvILF-0003fx-5U for ged-emacs-devel@m.gmane.org; Mon, 04 Jun 2007 21:35:49 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HvILE-0003wC-Mg for ged-emacs-devel@m.gmane.org; Mon, 04 Jun 2007 15:35:48 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HvILB-0003w7-Rt for emacs-devel@gnu.org; Mon, 04 Jun 2007 15:35:45 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HvIL9-0003vu-G8 for emacs-devel@gnu.org; Mon, 04 Jun 2007 15:35:44 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HvIL9-0003vp-Ax for emacs-devel@gnu.org; Mon, 04 Jun 2007 15:35:43 -0400 Original-Received: from heller.inter.net.il ([213.8.233.23]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HvIL8-0003Hz-RV for emacs-devel@gnu.org; Mon, 04 Jun 2007 15:35:43 -0400 Original-Received: from HOME-C4E4A596F7 (IGLD-84-229-238-199.inter.net.il [84.229.238.199]) by heller.inter.net.il (MOS 3.7.3a-GA) with ESMTP id CSU15633 (AUTH halo1); Mon, 4 Jun 2007 22:35:08 +0300 (IDT) In-reply-to: <878xb05ras.fsf@stupidchicken.com> (message from Chong Yidong on Sun, 03 Jun 2007 23:31:23 -0400) X-detected-kernel: FreeBSD 4.7-5.2 (or MacOS X 10.2-10.4) (2) 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:72226 Archived-At: > From: Chong Yidong > Date: Sun, 03 Jun 2007 23:31:23 -0400 > > 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? > If so, I think a reasonable procedure we can follow is to (i) go ahead > and start merging *bugfixes* from the trunk into the branch, and (ii) > make a request to emacs-devel for each new *feature* from the trunk > that we want to add to the branch. FWIW, I don't think we should merge changes that are safe until some time has passed and we have some kind of idea about how buggy v22.1 is. If the number of problems we hear on bug-gnu-emacs is large, then we should stabilize 22.x before we merge changes that can potentially destabilize it.