From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Don Armstrong Newsgroups: gmane.emacs.devel Subject: Re: Debbugs testbed Date: Tue, 19 Feb 2008 23:16:11 -0800 Message-ID: <20080220071611.GS5438@volo.donarmstrong.com> References: <20080220021827.GR1092@rzlab.ucr.edu> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1203533210 21521 80.91.229.12 (20 Feb 2008 18:46:50 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 20 Feb 2008 18:46:50 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Feb 20 19:47:13 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JRtyG-00033V-TS for ged-emacs-devel@m.gmane.org; Wed, 20 Feb 2008 19:47:09 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JRtxm-00051N-1Y for ged-emacs-devel@m.gmane.org; Wed, 20 Feb 2008 13:46:38 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JRjBk-0002P2-So for emacs-devel@gnu.org; Wed, 20 Feb 2008 02:16:20 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JRjBg-0002Oe-B6 for emacs-devel@gnu.org; Wed, 20 Feb 2008 02:16:20 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JRjBf-0002Ob-Sj for emacs-devel@gnu.org; Wed, 20 Feb 2008 02:16:16 -0500 Original-Received: from rzlab.ucr.edu ([138.23.92.77]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1JRjBf-0004jU-Hl for emacs-devel@gnu.org; Wed, 20 Feb 2008 02:16:15 -0500 Original-Received: from rzlab.ucr.edu (rzlab.ucr.edu [127.0.0.1]) by rzlab.ucr.edu (8.13.8/8.13.8/Debian-3) with ESMTP id m1K7GCQO022740 for ; Tue, 19 Feb 2008 23:16:12 -0800 Original-Received: (from remotemail@localhost) by rzlab.ucr.edu (8.13.8/8.13.8/Submit) id m1K7GCh3022739 for emacs-devel@gnu.org; Tue, 19 Feb 2008 23:16:12 -0800 Original-Received: (nullmailer pid 3104 invoked by uid 1000); Wed, 20 Feb 2008 07:16:11 -0000 Mail-Followup-To: emacs-devel@gnu.org Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17+20080114 (2008-01-14) X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 3) X-Mailman-Approved-At: Wed, 20 Feb 2008 13:46:12 -0500 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:89723 Archived-At: On Wed, 20 Feb 2008, =C3=93scar Fuentes wrote: > First: it has no web interface for filling bugs: an easy and > intuitive interface for users is paramount. One of the summer of code projects for 2007 was to create one, and it does work. Secondly, it's not like it would be all that difficult for someone to create one either; all it needs to do is take a list of "components", and gate the program field to e-mail and send it to submit@. [The sumer of code project does way more, including modifying the status of bugs.] > Second: IMO, it is complex. Look at what you are expected to read > just for sending a bug: >=20 > http://emacsbugs.donarmstrong.com/Reporting We generally suggest that people use reportbug to do it, and it wouldn't be all that difficult to handle dealing with submissions that didn't fit that format by assigning them to a general package. [The reason why Debian doesn't is because typically bugs filed by people who are unable to follow those instructions or run reportbug tend to be useless.] > See the interface for querying the bug database: >=20 > http://emacsbugs.donarmstrong.com/ >=20 > and after all that those checkboxes you can't ask simple things like > "bugs reported for Emacs v 22.1 or later". You actually can, but it requires knowing how to generate the urls manually. That's actually one of the next things to improve on my todo list, as that selection form is nearly useless.[1] For example, in Debian you'd be looking at something like: http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=3Demacs22;version=3D22.1%2= B1-1 which would tell you about the bugs which are known to affect version 22.1+1-1 of the emacs22 package. > Third: Ironically, the mail message containing the bug report has a > simple format, once you know the component (package, on debian > parlance) and version. But this is not easy to do. `cc-mode' is not > the same as `c-mode', and `auctex' is not under the Emacs project. A > web interface can show a list of known components for the user to > pick. Sure, but it's not a big deal even if users don't know the component. Debian has a 'general' pseudopackage for precisely this reason. Developers who know better simply send a message to reassign the bug to the proper component. (Users who don't know the components already will almost invariably get them wrong anyway.) In any event, it's entirely up to you all to figure out whether what debbugs does or doesn't do will work for you, and if you decide to use it, what changes are needed to make it optimal. Don Armstrong 1: Patches are always accepted, the bzr is here: http://bugs.debian.org/debbugs-source/ --=20 Any excuse will serve a tyrant. -- Aesop http://www.donarmstrong.com http://rzlab.ucr.edu