From: phillip.lord@russet.org.uk (Phillip Lord)
To: Andrew Hyatt <ahyatt@gmail.com>
Cc: Nikolaus Rath <Nikolaus@rath.org>,
Drew Adams <drew.adams@oracle.com>,
emacs-devel@gnu.org
Subject: Re: Basic questions about the triage process
Date: Thu, 07 Jan 2016 21:09:10 +0000 [thread overview]
Message-ID: <87r3htjdvt.fsf@russet.org.uk> (raw)
In-Reply-To: <m2h9j0ketn.fsf@gmail.com> (Andrew Hyatt's message of "Tue, 29 Dec 2015 18:36:20 -0500")
Is there a "pending-closure" tag, that can be used to help the clean up?
Then one person could send the "I think this is outdated now" email, and
another close it later.
Phil
Andrew Hyatt <ahyatt@gmail.com> writes:
> Sounds like there's some widespread feeling that we should ask first
> regardless of how much time has passed. The difference seems a bit minor
> to me (the real issue is the languishing of bugs, I think), because the
> only difference is whether we close before the email or after waiting
> for a response. But I'll just ask first, give people a few weeks to
> respond, and then close the bug if there's no response.
>
> FWIW, on the bugs I looked at yesterday, a few bounced from the
> reporter's email, so I'll just close them immediately if that happens.
>
> Drew Adams <drew.adams@oracle.com> writes:
>
>>> > To me, it feels a bit
>>> > awkward to suddenly ask people to confirm anything after years have
>>> > passed - just closing seems like a more reasonable approach to me.
>>>
>>> As a reporter, I can assure you that I feel exactly the other way
>>> around. It takes time to write good bugreports, and if they languish for
>>> several years only to eventually get closed because they "seem to have
>>> been fixed" makes me angry.
>>>
>>> I consider a polite "I tried to reproduce it
>>> but failed, could you confirm that this is fixed for you as well?" to be
>>> much more respectful of my time and contribution.
>>
>> 100% agreement. Users who write bug reports are helping.
>> Even more important: they are actively _trying_ to help.
next prev parent reply other threads:[~2016-01-07 21:09 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-28 5:39 Basic questions about the triage process Andrew Hyatt
2015-12-28 8:58 ` Michael Albinus
2015-12-28 16:25 ` Andrew Hyatt
2015-12-28 17:35 ` Michael Albinus
2015-12-28 20:24 ` John Wiegley
2015-12-29 5:40 ` Andrew Hyatt
2015-12-29 17:12 ` Eli Zaretskii
2015-12-30 0:22 ` Andrew Hyatt
2015-12-30 17:21 ` Eli Zaretskii
2015-12-31 1:19 ` Noam Postavsky
2015-12-31 3:38 ` Eli Zaretskii
2015-12-31 9:06 ` Michael Albinus
2015-12-31 13:49 ` Eli Zaretskii
2015-12-31 13:57 ` Michael Albinus
2016-01-07 21:04 ` Phillip Lord
2016-01-07 22:05 ` Andy Moreton
2016-01-07 22:40 ` Phillip Lord
2016-01-09 3:46 ` Andrew Hyatt
2015-12-28 23:55 ` Xue Fuqiao
2015-12-29 0:38 ` Andrew Hyatt
2015-12-29 0:50 ` Lars Ingebrigtsen
2015-12-29 0:59 ` Andrew Hyatt
2015-12-29 1:07 ` Lars Ingebrigtsen
2015-12-29 1:21 ` John Wiegley
2015-12-29 1:50 ` Drew Adams
2016-01-02 21:37 ` Marcin Borkowski
2016-02-15 20:04 ` Marcin Borkowski
2015-12-29 6:46 ` CHENG Gao
2015-12-29 15:50 ` Eli Zaretskii
2015-12-29 17:03 ` Nikolaus Rath
2015-12-29 17:16 ` John Wiegley
2015-12-29 17:50 ` Drew Adams
2015-12-29 23:36 ` Andrew Hyatt
2016-01-07 21:09 ` Phillip Lord [this message]
2016-01-07 21:28 ` Lars Magne Ingebrigtsen
2016-01-09 3:47 ` Andrew Hyatt
2016-01-09 20:56 ` John Wiegley
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=87r3htjdvt.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=Nikolaus@rath.org \
--cc=ahyatt@gmail.com \
--cc=drew.adams@oracle.com \
--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 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).