From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brian Wightman Subject: Re: [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines Date: Wed, 2 Nov 2011 07:57:36 -0500 Message-ID: References: <87pqhrih3s.fsf@gmail.com> <87zkgvgxe7.fsf@gmail.com> <1405.1319147324@alphaville.dokosmarshall.org> <87zkgvfhra.fsf@gmail.com> <2127.1319148505@alphaville.dokosmarshall.org> <87vcrjfgt1.fsf@gmail.com> <80sjmmvm60.fsf@somewhere.org> <4EA129DB.4070006@christianmoe.com> <8762ji5jr6.fsf@gmail.com> <4EA1D4F9.5010302@christianmoe.com> <4ea1de9c.67b4ec0a.553d.122a@mx.google.com> <87aa8t10np.fsf@gmail.com> <4ea5a95b.059dec0a.606e.0c92@mx.google.com> <874nypkn6y.fsf@gmail.com> <87obwwkia5.fsf@gmail.com> <87boswk4vj.fsf@gmail.com> <8627.1320157576@alphaville.dokosmarshall.org> <9991.1320159724@alphaville.dokosmarshall.org> <87hb2nj2ic.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: Received: from eggs.gnu.org ([140.186.70.92]:43146) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RLaNz-00008A-28 for emacs-orgmode@gnu.org; Wed, 02 Nov 2011 08:57:47 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RLaNu-00037N-Eh for emacs-orgmode@gnu.org; Wed, 02 Nov 2011 08:57:43 -0400 Received: from mail-qw0-f41.google.com ([209.85.216.41]:35096) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RLaNu-000376-C4 for emacs-orgmode@gnu.org; Wed, 02 Nov 2011 08:57:38 -0400 Received: by qadc11 with SMTP id c11so165513qad.0 for ; Wed, 02 Nov 2011 05:57:37 -0700 (PDT) In-Reply-To: <87hb2nj2ic.fsf@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org On Tue, Nov 1, 2011 at 10:17 AM, Eric Schulte wrote: > This is also after all the development repository, and while I do try > very hard never to break this head of this repository at the same time I > think it is an acceptable place to try out new functionality. Given that a common recommendation for a bug fix is to 'try commit blah blah blah', would it make sense to have bug fixes go onto a 'maint' branch (as well as master), and new features / changed features stay on the master branch? At the time when 'master' is ready for a new official release, it could then be merged into 'maint' to create the next stable point for bug fixes. Adding features on the same branch as bug fixes, when 'official releases' are not made frequently seems to be a formula for frustration. Thoughts? Brian