From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Juanma Barranquero Newsgroups: gmane.emacs.devel Subject: Re: Bug tracking Date: Mon, 14 Jun 2004 01:03:16 +0200 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <20040614005304.E187.LEKTU@mi.madritel.es> References: <20040612143605.151D.LEKTU@mi.madritel.es> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1087167830 27640 80.91.224.253 (13 Jun 2004 23:03:50 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 13 Jun 2004 23:03:50 +0000 (UTC) Cc: Richard Stallman Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Mon Jun 14 01:03:43 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 1BZe0t-0001wN-00 for ; Mon, 14 Jun 2004 01:03:43 +0200 Original-Received: from lists.gnu.org ([199.232.76.165]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BZe0t-0001ZF-00 for ; Mon, 14 Jun 2004 01:03:43 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BZe1k-0002kH-5O for emacs-devel@quimby.gnus.org; Sun, 13 Jun 2004 19:04:36 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BZe1d-0002jQ-IA for emacs-devel@gnu.org; Sun, 13 Jun 2004 19:04:29 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BZe1b-0002ir-CD for emacs-devel@gnu.org; Sun, 13 Jun 2004 19:04:28 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BZe1a-0002in-UE for emacs-devel@gnu.org; Sun, 13 Jun 2004 19:04:27 -0400 Original-Received: from [62.81.186.18] (helo=smtp08.retemail.es) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BZe0V-0003vA-Rl; Sun, 13 Jun 2004 19:03:20 -0400 Original-Received: from [127.0.0.1] ([213.37.34.195]) by smtp08.retemail.es (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP id <20040613230318.VMW3295.smtp08.retemail.es@[127.0.0.1]>; Mon, 14 Jun 2004 01:03:18 +0200 Original-To: emacs-devel@gnu.org In-Reply-To: X-Mailer: Becky! ver. 2.09.01 [en] 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:24938 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:24938 On Sun, 13 Jun 2004 17:49:32 -0400, Richard Stallman wrote: > 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. I don't have specific systems in mind. I've seen one or two that could be useful (Mantis, for example), because they seem easy. But I'm not married to any one answer. > The number of issues we want to record should not be as much as 50. You and I are talking about different things. I brought this up with regards to issues unfinished, from a release POV. I'm not sure what you include in that category: documentation to write, unfinished features, etc. But I certainly include in it bug reports, so I cannot put a limit on "the issues I want to record" of 50 or 100 or any other number. > 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. [...] > 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. I was talking about rejected bug reports, of course. The ones that are determined not to be a bug after all. > Perhaps you are envisioning a bug tracking system. That's not what > this we're trying to do here. Richard, excuse me, but till three days ago, no one was "trying to do" anything on this matter (in general; of course each one of us has their particular TODO). What you now want to do is clear, and what I'm interested in doing is too, and they aren't the same thing. I accept the decision, as you said; i.e., if you create an etc/ISSUES and put in it things to do, I'll use it. But this has *nothing* to do with having or not having a bug/issue tracker. You're talking of a planner of sorts. /L/e/k/t/u