From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: phillip.lord@russet.org.uk (Phillip Lord) Newsgroups: gmane.emacs.devel Subject: Re: 4K Bugs Date: Fri, 08 Jan 2016 12:48:02 +0000 Message-ID: <87lh80b5kt.fsf@russet.org.uk> References: <87mvszdp6b.fsf@gnus.org> <8737u9kv6f.fsf@russet.org.uk> <87oacwq240.fsf@gmail.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1452257376 12805 80.91.229.3 (8 Jan 2016 12:49:36 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 8 Jan 2016 12:49:36 +0000 (UTC) Cc: emacs-devel@gnu.org To: Alexis Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jan 08 13:49:31 2016 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 1aHWTy-0000Ky-5X for ged-emacs-devel@m.gmane.org; Fri, 08 Jan 2016 13:49:30 +0100 Original-Received: from localhost ([::1]:35458 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aHWTx-0007Ss-NX for ged-emacs-devel@m.gmane.org; Fri, 08 Jan 2016 07:49:29 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:53025) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aHWSd-00052T-Qy for emacs-devel@gnu.org; Fri, 08 Jan 2016 07:48:08 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aHWSa-0005h1-HT for emacs-devel@gnu.org; Fri, 08 Jan 2016 07:48:07 -0500 Original-Received: from cheviot22.ncl.ac.uk ([128.240.234.22]:58596) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aHWSa-0005gj-B1 for emacs-devel@gnu.org; Fri, 08 Jan 2016 07:48:04 -0500 Original-Received: from smtpauth-vm.ncl.ac.uk ([10.8.233.129] helo=smtpauth.ncl.ac.uk) by cheviot22.ncl.ac.uk with esmtp (Exim 4.63) (envelope-from ) id 1aHWSY-0000cU-E7; Fri, 08 Jan 2016 12:48:02 +0000 Original-Received: from jangai.ncl.ac.uk ([10.66.67.223] helo=localhost) by smtpauth.ncl.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.63) (envelope-from ) id 1aHWSY-0005N7-5x; Fri, 08 Jan 2016 12:48:02 +0000 In-Reply-To: <87oacwq240.fsf@gmail.com> (Alexis's message of "Fri, 8 Jan 2016 12:41:35 +1100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 128.240.234.22 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:197816 Archived-At: Alexis writes: > i've just recently installed the `debbugs` package myself, as part of trying > to help out with bug triage. i rather like it overall, and find it less > unwieldy than the Web UI - thanks to those who have put it together! Still, i > too have had some issues: > > Phillip Lord writes: > >> - After installing debbugs, there is no obvious entry point. M-x >> debugs-[tab] gives 30 different commands. > > Agreed; it took me a few moments to realise that debbugs-gnu was probably what > i wanted. Turns out that either "-gnu" or "-org" works fine. They just produce a different UI. I think aliasing debbugs-gnu to debbugs would help. >> - debbugs-gnu list bugs from number 158 and upward; the entire first >> 500 is about emacs 23 pre-releases. If I want to get the latest bugs, >> they are on page 5. > > An argument could be made that the longest-outstanding issues should be > displayed first, to try to encourage their resolution. Having said that, it > could also be argued that their longevity means they're less likely to be able > to be resolved soon than recent bugs. So i'm not sure what the best default is > here. I am very suspiscious about that. Most issue trackers are "most recent first". > >> - On none of the debbugs pages are there any obvious menu items or >> bug-related functionality. > > Well, as usual in these situations, i used C-h m (`describe-mode`) to find out > what i can do; but yes, it might be useful to at least have one or two lines > of text describing at least some of the possible commands (and maybe also, > what the colours in the `State` field indicate). > >> - I found out about hitting "C" to send a control message. Configuring >> this to "mail client" and up pops thunderbird, although I am a Gnus user. > > i'm a mu4e user, and when i try to send a control message .... Well, i'm not > sure what happens. i get nothing to indicate a message was sent, but nothing > to indicate it failed to be sent either. i can successfully use mu4e to reply > to messages in the relevant bug thread, though. And there is no where to practice! I might create a bug report just so I can try setting some control messages on it. > Finally, i'd like to suggest that the `debbugs` manual be renamed to something > like `debbugs-dev`, and the `debbugs-ug` manual be renamed to `debbugs`. In > trying to find out what the colours in the `State` field indicated, i ran the > `info-display-manual` command and specified `debbugs`; the result ("Debbugs > Programmers Manual") surprised me, and it took me a while to realise that > there's a `debbugs-ug` ("Debbugs User Guide") manual. My guess is that many > more people are going to want to use the latter than the former; hence my > rename suggestion. Perhaps it might also be useful to link to the User Guide > from the `debbugs` UI? Yes, this makes sense to me also. Phil