From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Eric S. Raymond" Newsgroups: gmane.emacs.devel Subject: Re: Why Emacs needs a modern bug tracker Date: Fri, 4 Jan 2008 13:29:50 -0500 Organization: Eric Conspiracy Secret Labs Message-ID: <20080104182950.GE18314@thyrsus.com> References: <20080104164454.0A4BD830697@snark.thyrsus.com> <200801041833.37632.andreas.roehler@online.de> Reply-To: esr@thyrsus.com NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1199471603 11862 80.91.229.12 (4 Jan 2008 18:33:23 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 4 Jan 2008 18:33:23 +0000 (UTC) Cc: "Eric S. Raymond" , Stefan Monnier , emacs-devel@gnu.org To: Andreas =?iso-8859-1?Q?R=F6hler?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jan 04 19:33:39 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 1JArMQ-0005pg-Av for ged-emacs-devel@m.gmane.org; Fri, 04 Jan 2008 19:33:38 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JArM3-0005Hc-SX for ged-emacs-devel@m.gmane.org; Fri, 04 Jan 2008 13:33:15 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JArIW-0002mF-OI for emacs-devel@gnu.org; Fri, 04 Jan 2008 13:29:36 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JArIV-0002kw-Mc for emacs-devel@gnu.org; Fri, 04 Jan 2008 13:29:35 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JArIV-0002kp-Cl for emacs-devel@gnu.org; Fri, 04 Jan 2008 13:29:35 -0500 Original-Received: from static-71-162-243-5.phlapa.fios.verizon.net ([71.162.243.5] helo=snark.thyrsus.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JArIV-0003P6-AB for emacs-devel@gnu.org; Fri, 04 Jan 2008 13:29:35 -0500 Original-Received: by snark.thyrsus.com (Postfix, from userid 23) id 2DF3A830697; Fri, 4 Jan 2008 13:29:50 -0500 (EST) Content-Disposition: inline In-Reply-To: <200801041833.37632.andreas.roehler@online.de> X-Eric-Conspiracy: There is no conspiracy User-Agent: Mutt/1.5.15+20070412 (2007-04-11) X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 3) 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:86074 Archived-At: Andreas R=F6hler : > Concerning the bugtracking: a lot of bugs reported > aren't really one. That can't be changed. What with all > this false bugs in a database? The Wesnoth bug/issue tracker has statuses "Wont Fix" and "Invalid". =20 Our devs apply these according to their judgment. Such decisions have implicit review because everyone on the bug-notification email list sees the status changes. Sometimes, another dev will change the tagging, explaining why in a comment. =20 At each release we close bugs still marked Invalid or Wont Fix. =20 > OTOH some severe bugs seem reported from time to time, > but not fixed so far. Will a database change that? Not directly, no. But it will help focus attention on the most important bugs. > What about some kind of a blackboard, establishing a > hierarchy of important bugs naming a person in charge > for it? Two of the main purposes of a tracker are (1) to make bug priority apparent, and (b) to document who, if anyone, has taken responsibility for each bug. --=20 Eric S. Raymond