From: Daniel Colascione <dancol@dancol.org>
To: Leo <sdl.web@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: why bugs only fixed in trunk?
Date: Tue, 25 Dec 2012 17:44:46 -0800 [thread overview]
Message-ID: <50DA568E.4080505@dancol.org> (raw)
In-Reply-To: <m2ehidtxsu.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 556 bytes --]
On 12/25/2012 5:19 PM, Leo wrote:
> One of the incentives to report bugs in the pretest is to have them
> squashed before the release. Unfortunately it seems most bugs are just
> fixed in trunk (which could mean wait another year for the fix) even if
> reported against a pretest build.
>
> Is there an implicitly agreed practice here?
The trunk is in stabalization mode right now: only critical bugfixes and
regressions can go in. The sooner we get 24.3 out the door, the sooner we can
release a 24.4 with all the bugfixes you mention.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 258 bytes --]
next prev parent reply other threads:[~2012-12-26 1:44 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 [this message]
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
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=50DA568E.4080505@dancol.org \
--to=dancol@dancol.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).