From: John Wiegley <jwiegley@gmail.com>
To: Andrew Hyatt <ahyatt@gmail.com>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: Basic questions about the triage process
Date: Mon, 28 Dec 2015 12:24:55 -0800 [thread overview]
Message-ID: <m2a8ous4mg.fsf@newartisans.com> (raw)
In-Reply-To: <CAM6wYYJT6OJNmcBjLMv8kVdqpnBF828eF4VqnmxaDV7c=uJFtA@mail.gmail.com> (Andrew Hyatt's message of "Mon, 28 Dec 2015 05:39:04 +0000")
[-- Attachment #1: Type: text/plain, Size: 1705 bytes --]
>>>>> Andrew Hyatt <ahyatt@gmail.com> writes:
> 1) How to identify the bugs to be triaged. I actually don't know the set of
> bugs you are interested in. All the open ones? Just the ones blocking emacs
> 25? If I'm using the debbugs package, what's the command I use to display
> just the set we're interested in?
There are really two sets of bugs we'd like to pay attention to:
1. Those blocking the release of Emacs 25. Clearly, we can't release until
this reaches zero.
2. All the open bugs, especially the oldest ones. If they don't reproduce
against emacs-25 anymore, we'd like to mark them closed as fixed in that
release.
#1 is a fairly small list, so just getting more information on those bugs so
that the developers know how to proceed next is what's important.
#2 is a large list, but would help out the Emacs project by clearing out
things we don't need to pay attention to anymore.
> Also, what if it does reproduce? I guess just a reply saying that it
> reproduces? Or does it need to be tagged in some way?
A comment would be valuable, and if what you saw still matches the description
of the problem.
> Sorry, maybe there was a document that explains this all, and I missed it.
> If there's isn't such a document, I think it'd be pretty helpful.
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.
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 629 bytes --]
next prev parent reply other threads:[~2015-12-28 20:24 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 [this message]
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
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=m2a8ous4mg.fsf@newartisans.com \
--to=jwiegley@gmail.com \
--cc=ahyatt@gmail.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).