all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lennart Borgman <lennart.borgman@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: Emacs-Devel devel <emacs-devel@gnu.org>
Subject: Re: The art of closing bug reports
Date: Sun, 10 Jul 2011 03:18:15 +0200	[thread overview]
Message-ID: <CANbX3669W=rYLODPMHC4YiYDBnGMmNawBDc7Yz9X0Hx+XrphQA@mail.gmail.com> (raw)
In-Reply-To: <3qliw7eyn3.fsf@fencepost.gnu.org>

On Sun, Jul 10, 2011 at 03:02, Glenn Morris <rgm@gnu.org> wrote:
>
>>> I am a bit disturbed by bug reports that are closed without much
>>> effort trying to understand if the bugs are still there.
>
> There is also an "art" to opening bug reports. It's well documented, and
> many people manage to do it. I'm sorry to say, but some bug reports are
> of such low quality that they essentially have no value. Leaving them
> open does nothing except dilute attention away from other reports where
> progress can be made.

Since I happen to manage many bug reports myself I have some
experience with this. I close bug reports that I can't reproduce and
get no feedback on. But I do not do that if I just do not have time to
reproduce them. Then I just leave them since they might be valuable
further on.



  reply	other threads:[~2011-07-10  1:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-10  0:40 The art of closing bug reports Lennart Borgman
2011-07-10  0:52 ` Juanma Barranquero
2011-07-10  0:56   ` Lennart Borgman
2011-07-10  1:31     ` Juanma Barranquero
2011-07-10  2:03       ` Lennart Borgman
2011-07-10  5:19         ` Tim Cross
2011-07-10  9:43           ` Drew Adams
2011-07-10  1:02   ` Glenn Morris
2011-07-10  1:18     ` Lennart Borgman [this message]
2011-07-10  8:16       ` Bastien

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='CANbX3669W=rYLODPMHC4YiYDBnGMmNawBDc7Yz9X0Hx+XrphQA@mail.gmail.com' \
    --to=lennart.borgman@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=rgm@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.