all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: emacs-devel@gnu.org
Subject: Suggestion to indicate fixed version when closing a bug
Date: Sat, 10 Dec 2011 02:57:59 -0500	[thread overview]
Message-ID: <g21uscn9iw.fsf@fencepost.gnu.org> (raw)


Hi,

When you close a debbugs.gnu.org report as fixed, I suggest indicating
the version in which the fix was applied.

If you use the 123-done way of closing a bug, just put:

Version: 24.1

at the first line of the body.

If you use the control@debbugs + close syntax, then just use:

close 123 24.1


The version number should be the first one in which a fix is present.
For a bug fixed today, this would be 24.1, but during pretesting I think
it is helpful to use the version of the next pretest (ie, 24.0.93).
(I don't think it will matter later on if a pretest version number turns
out not to exist because the actual release was made.)



             reply	other threads:[~2011-12-10  7:57 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-10  7:57 Glenn Morris [this message]
2011-12-10  8:38 ` Suggestion to indicate fixed version when closing a bug Eli Zaretskii
2011-12-10 19:10   ` Glenn Morris
2011-12-10 19:13     ` Glenn Morris
2011-12-10 19:31     ` Lennart Borgman
2011-12-10 19:43     ` Eli Zaretskii
2011-12-10 20:55       ` Glenn Morris
2011-12-10 21:08         ` Eli Zaretskii
2011-12-10 21:17           ` Glenn Morris
2011-12-10 21:20             ` Karl Fogel
2011-12-11  5:34               ` Eli Zaretskii
2011-12-11  6:32                 ` Karl Fogel
2011-12-11 17:37               ` Stephen J. Turnbull
2011-12-10 21:17       ` Karl Fogel
2011-12-10 21:20         ` Glenn Morris
2011-12-10 22:53           ` Glenn Morris
2011-12-11  5:33             ` Eli Zaretskii
2011-12-12  0:06               ` Glenn Morris
2011-12-12  8:40                 ` Lars Magne Ingebrigtsen
2011-12-10 19:28   ` Karl Fogel
2011-12-10 19:44     ` Eli Zaretskii
2011-12-12 16:41 ` Stefan Monnier

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

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

  git send-email \
    --in-reply-to=g21uscn9iw.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.