From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eric Schulte Newsgroups: gmane.emacs.devel Subject: Re: Merging Org 7.8.02 before Emacs 24.1 Date: Mon, 26 Dec 2011 14:32:01 -0700 Message-ID: <87boqv58a6.fsf@gmx.com> References: <877h1ncs1u.fsf@altern.org> <87ipl3g4jr.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1324935145 8111 80.91.229.12 (26 Dec 2011 21:32:25 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 26 Dec 2011 21:32:25 +0000 (UTC) Cc: Bastien , "Jambunathan K." , schulte eric , emacs-devel@gnu.org To: Chong Yidong Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 26 22:32:20 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1RfI9b-0002o5-2t for ged-emacs-devel@m.gmane.org; Mon, 26 Dec 2011 22:32:19 +0100 Original-Received: from localhost ([::1]:44736 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RfI9a-00017U-GH for ged-emacs-devel@m.gmane.org; Mon, 26 Dec 2011 16:32:18 -0500 Original-Received: from eggs.gnu.org ([140.186.70.92]:45579) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RfI9Y-00017N-9n for emacs-devel@gnu.org; Mon, 26 Dec 2011 16:32:17 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RfI9V-0006nX-Si for emacs-devel@gnu.org; Mon, 26 Dec 2011 16:32:16 -0500 Original-Received: from mailout-us.gmx.com ([74.208.5.67]:49689) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1RfI9V-0006n6-OY for emacs-devel@gnu.org; Mon, 26 Dec 2011 16:32:13 -0500 Original-Received: (qmail invoked by alias); 26 Dec 2011 21:32:11 -0000 Original-Received: from c-174-56-1-147.hsd1.nm.comcast.net (EHLO bagel) [174.56.1.147] by mail.gmx.com (mp-us002) with SMTP; 26 Dec 2011 16:32:11 -0500 X-Authenticated: #67821228 X-Provags-ID: V01U2FsdGVkX18zCRhQtukz/efhsnHFBBPK1RdT9cgCdJCSjIW5xt xym/y/LUXSGcNe In-Reply-To: <87ipl3g4jr.fsf@gnu.org> (Chong Yidong's message of "Mon, 26 Dec 2011 15:44:56 +0800") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.92 (gnu/linux) X-Y-GMX-Trusted: 0 X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 74.208.5.67 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:146975 Archived-At: Chong Yidong writes: > Bastien writes: > >> 2. New Babel syntax: Eric Schulte went through a rich discussion with >> the Org Mode folks to simplify the syntax of code blocks. Releasing >> Emacs 24.1 with the old syntax would expose many users to bad habits >> and force us to strongly suggest using latest Org instead of the one >> that comes with Emacs. No one would benefit from this. > > Please provide some more information about the plan for Org development. > Suppose we merge 7.8.02 into trunk; what assurance would we have that, > within months, the Org team wouldn't switch tack and "strongly suggest" > the latest Org containing yet more features, rather than 7.8.02? That > would defeat the purpose of a feature freeze. >From the perspective of the Org-mode development mailing list this latest 7.8 release was seen as "the last chance" to make changes before the Emacs24 merge. Hence, many of the pending updates (e.g., the syntax standardization mentioned above) were specifically completed with the Emacs24 merge in mind. I can assure you that there will not be another patch between now and the Emacs24 release which we (the Org-mode devs) will recommend as strongly as this patch is recommended. However (as Bastien mentioned) development is ongoing and if the release of Emacs24 is truly many months down the line there is a possibility that another merge will be suggested. In either case I think merging 7.8.02 now would be for the best. Thanks, -- Eric Schulte http://cs.unm.edu/~eschulte/