From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: Bug tracking Date: Sat, 12 Jun 2004 18:38:29 +0300 Organization: JURTA Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <87zn78wzv6.fsf@mail.jurta.org> References: <87wu2dqij4.fsf@mail.jurta.org> <20040612143605.151D.LEKTU@mi.madritel.es> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1087055544 16236 80.91.224.253 (12 Jun 2004 15:52:24 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 12 Jun 2004 15:52:24 +0000 (UTC) Cc: rms@gnu.org, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Sat Jun 12 17:52:12 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 1BZAnk-0004o1-00 for ; Sat, 12 Jun 2004 17:52:12 +0200 Original-Received: from lists.gnu.org ([199.232.76.165]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BZAnk-0001Io-00 for ; Sat, 12 Jun 2004 17:52:12 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BZAoX-0002vW-MO for emacs-devel@quimby.gnus.org; Sat, 12 Jun 2004 11:53:01 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BZAoQ-0002vL-8k for emacs-devel@gnu.org; Sat, 12 Jun 2004 11:52:54 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BZAoO-0002uw-Br for emacs-devel@gnu.org; Sat, 12 Jun 2004 11:52:53 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BZAoO-0002ut-A2 for emacs-devel@gnu.org; Sat, 12 Jun 2004 11:52:52 -0400 Original-Received: from [66.33.219.4] (helo=spork.dreamhost.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BZAnT-00077y-Qp; Sat, 12 Jun 2004 11:51:55 -0400 Original-Received: from mail.jurta.org (80-235-41-87-dsl.mus.estpak.ee [80.235.41.87]) by spork.dreamhost.com (Postfix) with ESMTP id 3086311DC0B; Sat, 12 Jun 2004 08:51:53 -0700 (PDT) Original-To: Juanma Barranquero In-Reply-To: <20040612143605.151D.LEKTU@mi.madritel.es> (Juanma Barranquero's message of "Sat, 12 Jun 2004 14:47:45 +0200") User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3.50 (gnu/linux) 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:24879 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:24879 Juanma Barranquero writes: > There is flexibility and there is flexibility. Of course using a > custom-format, text file is the most flexible answer, at the cost of > having no tool other than what we want to develop. Yes, we have Emacs, > but even Emacs has no "Bug Tracker" major mode, that I know of :) Even without special mode a plain text file is the most convenient way to edit data and to perform arbitrary Emacs operations on them. > It doesn't have a web interface for other people, no automatic way > to extract statistics, it's *clumsy* beyond belief if you want to > also store past (and fixed or rejected) issues, has to be manually > edited by us so outside people cannot enter issues, I think there is nothing wrong with the fact that only Emacs developers will be able to fill bug reports. So no web interface is really needed. > needs that someone reads gnu-emacs-bugs@ reports and formats > them as desired That's exactly how it might work: developers read gnu-emacs-bugs, create new bug entries in the text file and commit them to CVS. And you can track changes in the text file with all the usual features of CVS. > it has limited posibilities for searching and categorizing... Apart from the Ee categorizing manager, I think that some other Emacs packages can perform these operations on text files. AFAIK, at least Gnus should be able to read a text file in the mail-like format and to treat it as a mail group with bug and TODO entries as messages. There are even many possibilities of tighter integration with its email functionality. -- Juri Linkov http://www.jurta.org/emacs/