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 00:52:01 +0200 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <20040614004350.E184.LEKTU@mi.madritel.es> References: <20040613030631.B099.LEKTU@mi.madritel.es> <87ekoj4fdc.fsf@mail.jurta.org> 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 1087167168 26439 80.91.224.253 (13 Jun 2004 22:52:48 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 13 Jun 2004 22:52:48 +0000 (UTC) Cc: Juri Linkov Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Mon Jun 14 00:52:39 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 1BZdqB-0001Tu-00 for ; Mon, 14 Jun 2004 00:52:39 +0200 Original-Received: from lists.gnu.org ([199.232.76.165]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BZdqA-0001RK-00 for ; Mon, 14 Jun 2004 00:52:38 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BZdr2-0007p2-6a for emacs-devel@quimby.gnus.org; Sun, 13 Jun 2004 18:53:32 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BZdr0-0007on-Ne for emacs-devel@gnu.org; Sun, 13 Jun 2004 18:53:30 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BZdqz-0007ob-4o for emacs-devel@gnu.org; Sun, 13 Jun 2004 18:53:30 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BZdqz-0007oY-0Y for emacs-devel@gnu.org; Sun, 13 Jun 2004 18:53:29 -0400 Original-Received: from [62.81.186.16] (helo=smtp06.retemail.es) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BZdpZ-0004eE-J1 for emacs-devel@gnu.org; Sun, 13 Jun 2004 18:52:02 -0400 Original-Received: from [127.0.0.1] ([213.37.34.195]) by smtp06.retemail.es (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP id <20040613225200.ABP18728.smtp06.retemail.es@[127.0.0.1]>; Mon, 14 Jun 2004 00:52:00 +0200 Original-To: emacs-devel@gnu.org In-Reply-To: <87ekoj4fdc.fsf@mail.jurta.org> 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:24937 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:24937 On Sun, 13 Jun 2004 19:00:47 +0300, Juri Linkov wrote: > Why _bound to reproduce_? ?? Because (IMHO) we need the functionality of an issue tracker, and we don't have it implemented. > Let's put it another way: we are > _motivated to create_ an Emacs-based issue tracker. No. Perhaps you're motivated to create an Emacs-based issue tracker. I'm just motivated to *use* an issue tracker, because I think quality would improve. I have not a single bit of interest in developing or helping to develop Yet Another Issue Tracker, and less so because there are quite a few free ones to pick from. > As for a web interface, I think it is not an absolute requirement, > and even often undesirable, since a better method for filing bugs > is `report-emacs-bug' which also adds all the necessary information > and doesn't require from Emacs users additional tools. I think we had already implicitly agreed to disagree on this one... Every program has a context. That doesn't mean that the users who take the trouble to file a bug report are unable to provide that information. report-emacs-bug is great, and if it can be integrated with an IT, wonderful. But surely is not a precondition. > Though, a some kind of an add-on HTTP<->CVS gateway could be > implemented to sync data between Savannah bug database and text > files in CVS repository, if that becomes absolutely necessary. "Could be implemented". Yeah. /L/e/k/t/u