From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Andrew Hyatt Newsgroups: gmane.emacs.devel Subject: Basic questions about the triage process Date: Mon, 28 Dec 2015 05:39:04 +0000 Message-ID: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a1145542eaaa2d70527eeb90c X-Trace: ger.gmane.org 1451281161 10055 80.91.229.3 (28 Dec 2015 05:39:21 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 28 Dec 2015 05:39:21 +0000 (UTC) To: "emacs-devel@gnu.org" , jwiegley@gmail.com Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 28 06:39:21 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aDQWe-0004R0-9m for ged-emacs-devel@m.gmane.org; Mon, 28 Dec 2015 06:39:20 +0100 Original-Received: from localhost ([::1]:43672 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aDQWd-0004ee-MQ for ged-emacs-devel@m.gmane.org; Mon, 28 Dec 2015 00:39:19 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:60384) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aDQWa-0004eY-49 for emacs-devel@gnu.org; Mon, 28 Dec 2015 00:39:16 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aDQWZ-00052i-5o for emacs-devel@gnu.org; Mon, 28 Dec 2015 00:39:16 -0500 Original-Received: from mail-vk0-x232.google.com ([2607:f8b0:400c:c05::232]:35582) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aDQWZ-00052d-1T for emacs-devel@gnu.org; Mon, 28 Dec 2015 00:39:15 -0500 Original-Received: by mail-vk0-x232.google.com with SMTP id k1so48021082vkb.2 for ; Sun, 27 Dec 2015 21:39:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=D7N6AqOKmVZcOnAFrfvRyhaBUO4iVUOmqodbHW7UJSw=; b=yuQu+l+wGZd/yWwRVoHzMtIiYBW1iEONKONLvygnHM5loIkqYAc1aFJbwoKcp3T/Q6 hcD+pL2LpIwri9lTpN6DQRdLfenLHmmAyBGfx3s42L/WY/o5go3URmqwAU6FVHqJ49gt PEqCJHLMUeCvrHqz1dfmdUM7vL5XSHrO+PvpS7QX6SybsMkmNUwE1iw3NgifYBZcDoyr B+osLU1+O4wNKdQQ/A4/a6RtfrgDlJUN/liLEAhcyM5FhBFCiYQkY4om/xq5leO9qkpG WLZp8Co8zrcFNz/RKyqTR8fNLIjLd+O0fO/+mgiTB7db84mIps4Kcse38/KHgef3mXx6 c8nQ== X-Received: by 10.31.8.83 with SMTP id 80mr34592128vki.105.1451281154218; Sun, 27 Dec 2015 21:39:14 -0800 (PST) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2607:f8b0:400c:c05::232 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:196993 Archived-At: --001a1145542eaaa2d70527eeb90c Content-Type: text/plain; charset=UTF-8 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. --001a1145542eaaa2d70527eeb90c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
John Wiegley recently put out a call on Twitter for people= to help with the closing out bugs against Emacs 25.=C2=A0 Seems like a rea= l problem.=C2=A0 I'd like to help!

But, pardon me fo= r my ignorance, but I'm a bit lost as to how to get started.=C2=A0 For = any bug triage, there's a few necessary steps you have to learn:
<= div>
1) How to identify the bugs to be triaged.=C2=A0 I actua= lly don't know the set of bugs you are interested in.=C2=A0 All the ope= n ones?=C2=A0 Just the ones blocking emacs 25?=C2=A0 If I'm using the d= ebbugs package, what's the command I use to display just the set we'= ;re interested in?

2) How to triage each bug.=C2= =A0 In this case, the basic task if clear: just try to reproduce against em= acs 25.=C2=A0 But if it doesn't reproduce, what then?=C2=A0 Do we close= the bug?=C2=A0 I downloaded and started using the debbugs package, but AFA= ICT, it's read-only.=C2=A0 Seems like it should be obvious, but I can&#= 39;t figure out how to close a bug in either debbugs package, or in the web= interface. =C2=A0

Also, what if it does reproduce= ?=C2=A0 I guess just a reply saying that it reproduces?=C2=A0 Or does it ne= ed to be tagged in some way?=C2=A0

Sorry, maybe th= ere was a document that explains this all, and I missed it.=C2=A0 If there&= #39;s isn't such a document, I think it'd be pretty helpful.
<= /div> --001a1145542eaaa2d70527eeb90c--