From: Andrew Hyatt <ahyatt@gmail.com>
To: phillip.lord@russet.org.uk (Phillip Lord)
Cc: Andy Moreton <andrewjmoreton@gmail.com>, emacs-devel@gnu.org
Subject: Re: Basic questions about the triage process
Date: Fri, 08 Jan 2016 22:46:14 -0500 [thread overview]
Message-ID: <m2y4bzo1o9.fsf@gmail.com> (raw)
In-Reply-To: <8737u9j9n9.fsf@russet.org.uk> (Phillip Lord's message of "Thu, 07 Jan 2016 22:40:42 +0000")
phillip.lord@russet.org.uk (Phillip Lord) writes:
> Andy Moreton <andrewjmoreton@gmail.com> writes:
>
>> On Thu 07 Jan 2016, Phillip Lord wrote:
>>
>>> Andrew Hyatt <ahyatt@gmail.com> writes:
>>>
>>>> John Wiegley <jwiegley@gmail.com> writes:
>>>>
>>>>>>>>>> Andrew Hyatt <ahyatt@gmail.com> writes:
>>>>>
>>>>> Perhaps we do need a targeted document for on-boarding bug herders. If, while
>>>>> you're learning this process, you could keep some notes on what helped you to
>>>>> get started, Andrew, that could become the start of such a document.
>>>>
>>>> I've put together my notes into a file I stuck in the admin section.
>>>> I'm attaching it as a patch. Feedback would be welcome, of course. I'm
>>>> guessing there's a few other things we'd like to put into this document
>>>> as well, but I won't attempt to go beyond just the basic triage
>>>> procedure we've discussed in this thread.
>>>
>>> Would you object to changing the name of this file to "bug-triage". It
>>> should say "bug" somewhere!
>>
>> Why ? Not all problems raised in an issue tracker are actually bugs
>> (user error, misconfiguration, distro packaging issues etc).
>
>
> "issue-triage" would also be fine. But "bug" is generally accepted here.
> "debbugs", "bugtracker" and so on.
>
> Just trying to increase discoverability.
I agree, I'll change this to bug-triage. FWIW, these systems always
seem to be referred to as bug systems, even though they always end up
handling other things besides bugs.
>
> Phil
next prev parent reply other threads:[~2016-01-09 3:46 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2y4bzo1o9.fsf@gmail.com \
--to=ahyatt@gmail.com \
--cc=andrewjmoreton@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=phillip.lord@russet.org.uk \
/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.