emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: Martyn Jago <martyn.jago@btinternet.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Should maint branch be deprecated?
Date: Tue, 20 Mar 2012 02:01:25 +0100	[thread overview]
Message-ID: <87d388f5lm.fsf@gnu.org> (raw)
In-Reply-To: <m2d3882rqj.fsf@btinternet.com> (Martyn Jago's message of "Mon, 19 Mar 2012 21:41:40 +0000")

Hi Martyn,

Martyn Jago <martyn.jago@btinternet.com> writes:

> As an infrequent committer to org-mode, I wonder if the maint branch is
> more pain than gain. 

It is a pain when too many things should happen on it.  

IMO It is a gain when we dedicate it to releases only.

No pain should come out of introducing hotfix-* branches, 
as they are transient branches.

Now I'm off to a well-deserved bed :)


  parent reply	other threads:[~2012-03-20  1:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-19 21:41 Should maint branch be deprecated? Martyn Jago
2012-03-19 22:41 ` Bastien
2012-03-19 23:12 ` Achim Gratz
2012-03-20  0:58   ` Bastien
2012-03-20  1:01 ` Bastien [this message]
2012-03-20  3:47   ` Martyn Jago

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d388f5lm.fsf@gnu.org \
    --to=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=martyn.jago@btinternet.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).