From: Andrew Hyatt <ahyatt@gmail.com>
To: "emacs-devel@gnu.org" <emacs-devel@gnu.org>, jwiegley@gmail.com
Subject: Basic questions about the triage process
Date: Mon, 28 Dec 2015 05:39:04 +0000 [thread overview]
Message-ID: <CAM6wYYJT6OJNmcBjLMv8kVdqpnBF828eF4VqnmxaDV7c=uJFtA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1220 bytes --]
John Wiegley recently put out a call on Twitter for people to help with the
closing out bugs against Emacs 25. Seems like a real problem. I'd like to
help!
But, pardon me for my ignorance, but I'm a bit lost as to how to get
started. For any bug triage, there's a few necessary steps you have to
learn:
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?
2) How to triage each bug. In this case, the basic task if clear: just try
to reproduce against emacs 25. But if it doesn't reproduce, what then? Do
we close the bug? I downloaded and started using the debbugs package, but
AFAICT, it's read-only. Seems like it should be obvious, but I can't
figure out how to close a bug in either debbugs package, or in the web
interface.
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?
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.
[-- Attachment #2: Type: text/html, Size: 1435 bytes --]
next reply other threads:[~2015-12-28 5:39 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-28 5:39 Andrew Hyatt [this message]
2015-12-28 8:58 ` Basic questions about the triage process 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
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='CAM6wYYJT6OJNmcBjLMv8kVdqpnBF828eF4VqnmxaDV7c=uJFtA@mail.gmail.com' \
--to=ahyatt@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jwiegley@gmail.com \
/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).