unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Leo <sdl.web@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: why bugs only fixed in trunk?
Date: Wed, 26 Dec 2012 11:59:25 +0100	[thread overview]
Message-ID: <87pq1x84fm.fsf@bzg.ath.cx> (raw)
In-Reply-To: <m2ehidtxsu.fsf@gmail.com> (Leo's message of "Wed, 26 Dec 2012 09:19:29 +0800")

Hi Leo,

Leo <sdl.web@gmail.com> writes:

> Long ago I used to report bugs in the org mode that was bundled with
> emacs but then the project's practice was to only fix in the development
> trunk. So I save myself some time stop reporting bugs there.

We all try hard so that all versions of Org are in an acceptable state.

There are mainly four versions:

1. Org in the bzr emacs-24 branch
2. Org in the bzr trunk branch
3. Org in the git maint branch
4. Org in the git master branch

I try to handle bugs from the bzr trunk and the git maint branches in
priority (as they are the "stable" versions), then from the trunk and
master (as "unstable" versions.)

I'm not syncing maint->emacs-24 and master->trunk regularily enough,
which might cause some frustration.  But in overall, the situation is
not that bad I think.

Let me know if you have any specific advice on how to make things
easier, either as a user or as a bug-reporter.

Thanks!

-- 
 Bastien



  parent reply	other threads:[~2012-12-26 10:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-26  1:19 why bugs only fixed in trunk? Leo
2012-12-26  1:44 ` Daniel Colascione
2012-12-26 12:43   ` Lars Ingebrigtsen
2012-12-26 16:34     ` Jay Belanger
2012-12-26 16:59       ` Bastien
2012-12-26 17:56         ` Daniel Colascione
2012-12-27  1:02           ` Leo
2012-12-27  3:48             ` Eli Zaretskii
2012-12-26  2:37 ` Chong Yidong
2012-12-26  4:50 ` Stephen J. Turnbull
2012-12-26  6:28 ` Jambunathan K
2012-12-26  7:00   ` Leo
2012-12-26  6:45 ` Xue Fuqiao
2012-12-26 10:59 ` Bastien [this message]
2012-12-26 12:04   ` Leo

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87pq1x84fm.fsf@bzg.ath.cx \
    --to=bzg@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=sdl.web@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

	https://git.savannah.gnu.org/cgit/emacs.git

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).