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: Re: Basic questions about the triage process Date: Mon, 28 Dec 2015 16:25:33 +0000 Message-ID: References: <8760zj2blv.fsf@gmx.de> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a1143e3dcb0b3fa0527f7c134 X-Trace: ger.gmane.org 1451319966 1392 80.91.229.3 (28 Dec 2015 16:26:06 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 28 Dec 2015 16:26:06 +0000 (UTC) Cc: jwiegley@gmail.com, "emacs-devel@gnu.org" To: Michael Albinus Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 28 17:26:05 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 1aDacX-0006lT-0y for ged-emacs-devel@m.gmane.org; Mon, 28 Dec 2015 17:26:05 +0100 Original-Received: from localhost ([::1]:45016 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aDacW-0004BU-G2 for ged-emacs-devel@m.gmane.org; Mon, 28 Dec 2015 11:26:04 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:50613) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aDacD-0004AF-GV for emacs-devel@gnu.org; Mon, 28 Dec 2015 11:25:46 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aDacC-0007Ot-75 for emacs-devel@gnu.org; Mon, 28 Dec 2015 11:25:45 -0500 Original-Received: from mail-vk0-x236.google.com ([2607:f8b0:400c:c05::236]:34425) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aDacC-0007OO-0O for emacs-devel@gnu.org; Mon, 28 Dec 2015 11:25:44 -0500 Original-Received: by mail-vk0-x236.google.com with SMTP id a123so22418115vkh.1 for ; Mon, 28 Dec 2015 08:25:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-type; bh=Iepg/l/9o5F/iQk4QZg1UebiXGY2Pfstm8WQgbHvncA=; b=cGK3HwPUW5C5HXwEeTErcZ2oLPdW/hn5oQHCSbxsyQkN519JKqMuBeIQbiL5uwxIG3 RUPqzwkS2C9J8ts2nOsGogdl6MOCqIKVEnW2IOmw0Eb4HKi3vwJdR3tVvxK0Tniic3Kf Z/CnunVvjqEcJVEzr2XjLnYxSe9PZ6Nr807wDXz3VTlSgNw3HGAgtGvjQrYJseP22BWV +zN1pnViwe4/JMvqnDsebXb4oDbB4/MgtL0VXQrs1o1IkbaXcp+bWrlbEkMFOFrA/WPk 3Mo8L1wvkEE8BQGGrnw0oXsgQ810vaAEoQ3l9cV5pW7UZ/9P1TdhX8W5THc5orW9xYOq XFeg== X-Received: by 10.31.172.135 with SMTP id v129mr16095766vke.154.1451319943538; Mon, 28 Dec 2015 08:25:43 -0800 (PST) In-Reply-To: <8760zj2blv.fsf@gmx.de> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2607:f8b0:400c:c05::236 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:197011 Archived-At: --001a1143e3dcb0b3fa0527f7c134 Content-Type: text/plain; charset=UTF-8 Thanks Michael, this is a really nice summary. One additional question: when looking at the open bugs, how do I know which ones have already been already tested against Emacs 25? I can see the Emacs 25 blockers, but probably not all the bugs that are reproducible in Emacs 25 are severe enough to be blockers, right? On Mon, Dec 28, 2015 at 3:58 AM Michael Albinus wrote: > Andrew Hyatt writes: > > Hi Andrew, > > > 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? > > debbugs on elpa is under rewrite these days, so I haven't pushed yet a > new version 0.8. Maybe you could download it from the elpa git? > > If you want to see just the open bugs, accept all default settings when > calling "M-x debbugs-gnu". You will see all open bugs with severity > serious, important or normal. 2142 lines just now. > > You can filter out the closed-but-not-archived-yet bugs by hitting "x" > (1906 lines). Hitting "x" again, all bug reports are shown again. > > If you want to filter the bugs, type "/ regexp". The regexp matches > strings in the report buffer. If you, for example, want to see all bugs > with the string "tramp" in the title, type "/ tramp". This gives you 14 > lines. Typing "w" returns to the full list of bugs. > > If you type "R", you will see all bugs blocking the next Emacs > release. 48 lines. You can combine it with a further "x", which results > in 33 not closed bugs blocking Emacs 25.1 release. These are the most > interesting bugs to be fixed. > > > 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. > > If your cursor points to the bug line you want to handle, type "C". This > starts a control message to be sent to the debbugs server. Use for > completion of possible actions. > > The debbugs elpa package comes with an info manual. > Try (info "(debbugs-ug)") Some commands I've mentioned above are not > documented in debbugs 0.7. See the info manual from the elpa repo. > > The file debbugs-gnu.el explains the keys also in its Commentary > section. > > Best regards, Michael. > --001a1143e3dcb0b3fa0527f7c134 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Thanks Michael, this is a really nice summary. =C2=A0
=
One additional question: when looking at the open bugs, how = do I know which ones have already been already tested against Emacs 25?=C2= =A0 I can see the Emacs 25 blockers, but probably not all the bugs that are= reproducible in Emacs 25 are severe enough to be blockers, right?

On Mon, Dec 28, 2015 at = 3:58 AM Michael Albinus <micha= el.albinus@gmx.de> wrote:
An= drew Hyatt <ahyatt= @gmail.com> writes:

Hi Andrew,

> 1) How to identify the bugs to be triaged. I actually don't know t= he
> 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 th= e
> command I use to display just the set we're interested in?

debbugs on elpa is under rewrite these days, so I haven't pushed yet a<= br> new version 0.8. Maybe you could download it from the elpa git?

If you want to see just the open bugs, accept all default settings when
calling "M-x debbugs-gnu". You will see all open bugs with severi= ty
serious, important or normal. 2142 lines just now.

You can filter out the closed-but-not-archived-yet bugs by hitting "x&= quot;
(1906 lines). Hitting "x" again, all bug reports are shown again.=

If you want to filter the bugs, type "/ regexp". The regexp match= es
strings in the report buffer. If you, for example, want to see all bugs
with the string "tramp" in the title, type "/ tramp". T= his gives you 14
lines. Typing "w" returns to the full list of bugs.

If you type "R", you will see all bugs blocking the next Emacs release. 48 lines. You can combine it with a further "x", which r= esults
in 33 not closed bugs blocking Emacs 25.1 release. These are the most
interesting bugs to be fixed.

> 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, wh= at
> then? Do we close the bug? I downloaded and started using the debbugs<= br> > package, but AFAICT, it's read-only. Seems like it should be obvio= us,
> but I can't figure out how to close a bug in either debbugs packag= e,
> or in the web interface.

If your cursor points to the bug line you want to handle, type "C"= ;. This
starts a control message to be sent to the debbugs server. Use <TAB> = for
completion of possible actions.

The debbugs elpa package comes with an info manual.
Try (info "(debbugs-ug)") Some commands I've mentioned above = are not
documented in debbugs 0.7. See the info manual from the elpa repo.

The file debbugs-gnu.el explains the keys also in its Commentary
section.

Best regards, Michael.
--001a1143e3dcb0b3fa0527f7c134--