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: Sun, 13 Jun 2004 17:49:32 -0400 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <87wu2dqij4.fsf@mail.jurta.org> <20040612143605.151D.LEKTU@mi.madritel.es> Reply-To: rms@gnu.org NNTP-Posting-Host: deer.gmane.org X-Trace: sea.gmane.org 1087163450 19344 80.91.224.253 (13 Jun 2004 21:50:50 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 13 Jun 2004 21:50:50 +0000 (UTC) Cc: juri@jurta.org, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Sun Jun 13 23:50:40 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 1BZcsC-0007Io-00 for ; Sun, 13 Jun 2004 23:50:40 +0200 Original-Received: from lists.gnu.org ([199.232.76.165]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BZcsC-0000en-00 for ; Sun, 13 Jun 2004 23:50:40 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BZct3-0006hu-Oy for emacs-devel@quimby.gnus.org; Sun, 13 Jun 2004 17:51:33 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BZcsv-0006hU-CP for emacs-devel@gnu.org; Sun, 13 Jun 2004 17:51:25 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BZcsu-0006hI-OA for emacs-devel@gnu.org; Sun, 13 Jun 2004 17:51:25 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BZcsu-0006h1-ML for emacs-devel@gnu.org; Sun, 13 Jun 2004 17:51:24 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BZcr7-000316-3p for emacs-devel@gnu.org; Sun, 13 Jun 2004 17:49:33 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1BZcr6-0008Sa-FE; Sun, 13 Jun 2004 17:49:32 -0400 Original-To: Juanma Barranquero In-reply-to: <20040612143605.151D.LEKTU@mi.madritel.es> (message from Juanma Barranquero on Sat, 12 Jun 2004 14:47:45 +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:24933 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:24933 I will not agree to use of a system that is hard for me to access, so we simply can't use the systems you have in mind. Please accept that decision. We will use a text file that I can access with CVS. The number of issues we want to record should not be as much as 50. It doesn't have a web interface for other people, It is not important for anyone to see this file except the Emcs developers, who will be looking for jobs they can work on to help make the release happen. no automatic way to extract statistics, The purpose of this database is to keep track of jobs that need to be done, for the release. We don't need statistics. They all will need to be done. it's *clumsy* beyond belief if you want to also store past (and fixed or rejected) issues, We can put the past issues into a DONE file in case anyone wants to look back at them. I don't know what you mean by "rejected" issues. If we don't believe a job needs to be done for the release, we won't ever put it in this file. Perhaps you are envisioning a bug tracking system. That's not what this we're trying to do here. has to be manually edited by us so outside people cannot enter issues, Only Emacs maintainers should edit this file. Outsiders cannot decide what jobs we need to do before the release, or mark them as done. needs that someone reads gnu-emacs-bugs@ reports and formats them as desired, That will be necessary no matter how we store the file. Only humans can decide what should go in the file. It cannot be done automatically. it has limited posibilities for searching and categorizing... We should not have so many items in the file that this becomes a significant issue.