From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: Bug tracking Date: Mon, 14 Jun 2004 14:50:05 -0400 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <20040512103042.FB57.JMBARRANQUERO@wke.es> <20040611122633.5F88.JMBARRANQUERO@wke.es> <87wu2dqij4.fsf@mail.jurta.org> <40CACF10.2050108@math.ku.dk> <863c4zy8mt.fsf@rumba.de.uu.net> Reply-To: rms@gnu.org NNTP-Posting-Host: deer.gmane.org X-Trace: sea.gmane.org 1087239061 781 80.91.224.253 (14 Jun 2004 18:51:01 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 14 Jun 2004 18:51:01 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Mon Jun 14 20:50:55 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1BZwXn-0000sU-00 for ; Mon, 14 Jun 2004 20:50:55 +0200 Original-Received: from lists.gnu.org ([199.232.76.165]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BZwXm-0001IV-00 for ; Mon, 14 Jun 2004 20:50:55 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BZwYf-0005uU-A2 for emacs-devel@quimby.gnus.org; Mon, 14 Jun 2004 14:51:50 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BZwY5-0005nK-SQ for emacs-devel@gnu.org; Mon, 14 Jun 2004 14:51:13 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BZwY3-0005i6-N3 for emacs-devel@gnu.org; Mon, 14 Jun 2004 14:51:12 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BZwY1-0005hd-GO for emacs-devel@gnu.org; Mon, 14 Jun 2004 14:51:11 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BZwWz-0008QV-OA for emacs-devel@gnu.org; Mon, 14 Jun 2004 14:50:05 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1BZwWz-0005ex-4I; Mon, 14 Jun 2004 14:50:05 -0400 Original-To: Kai Grossjohann In-reply-to: <863c4zy8mt.fsf@rumba.de.uu.net> (message from Kai Grossjohann on Sun, 13 Jun 2004 13:55:54 +0200) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.4 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:24959 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:24959 > We're not planning to use this to track individual bugs, Why not? I thought the discussion was about putting things reported by M-x report-emacs-bug RET into a database? No, this discussion is about tracking issues that need to be resolved before the release. Here is the message that raised this question: Still, the question remains: should we use some kind of issue tracker? Currently we have an etc/TODO, which is sort of half wish list, half grab bag of heterogeneous items. I'm all for using an issue tracker, if only because it makes easier to know where we are, release-wise, for any given release. For example, what's precluding us from doing a prerelease tarball just today (not that I'm proposing it, of course)? The answer to this question is not a list of bug reports; this job is not bug tracking. Tracking issues cannot mean bug tracking, because only something important qualifies as an "issue". A mere bug report is not (usually) an issue. On some occasions a certain bug report might be important enough to be an issue, but only the Emacs developers can decide when that is so. Only the developers can enter issues, and it makes no sense to have a large number of issues. A text file is the perfect way to keep track of issues. Bug tracking might be useful, but it is a completely different subject. If we use a bug-tracker, it should be easy to use via email and cvs.