From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Bastien Newsgroups: gmane.emacs.devel Subject: Re: Why Emacs needs a modern bug tracker Date: Sat, 05 Jan 2008 22:00:53 +0000 Message-ID: <87abnkq6ei.fsf@bzg.ath.cx> References: <20080104164454.0A4BD830697@snark.thyrsus.com> <20080104232514.GB2735@muc.de> <87r6gxoyjv.fsf@catnip.gol.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1199570515 12508 80.91.229.12 (5 Jan 2008 22:01:55 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 5 Jan 2008 22:01:55 +0000 (UTC) Cc: emacs-devel@gnu.org To: =?iso-8859-1?Q?=D3scar?= Fuentes Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jan 05 23:02:14 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JBH5o-0007GG-Bi for ged-emacs-devel@m.gmane.org; Sat, 05 Jan 2008 23:02:14 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JBH5N-0004sB-27 for ged-emacs-devel@m.gmane.org; Sat, 05 Jan 2008 17:01:45 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JBH5I-0004rg-Vf for emacs-devel@gnu.org; Sat, 05 Jan 2008 17:01:41 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JBH54-0004gx-9r for emacs-devel@gnu.org; Sat, 05 Jan 2008 17:01:40 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JBH54-0004gq-5m for emacs-devel@gnu.org; Sat, 05 Jan 2008 17:01:26 -0500 Original-Received: from hu-out-0506.google.com ([72.14.214.227]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JBH4w-0002yt-Bh for emacs-devel@gnu.org; Sat, 05 Jan 2008 17:01:25 -0500 Original-Received: by hu-out-0506.google.com with SMTP id 23so1013885huc.1 for ; Sat, 05 Jan 2008 14:00:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:received:from:to:cc:subject:in-reply-to:references:user-agent:date:message-id:mime-version:content-type:content-transfer-encoding:sender; bh=nQAFJ8woLpnsrvhoprTm+3KRmzeZCZL9Hzo5Kg+c1ns=; b=TNdUd3vbo60iP/Vf4NlJ6RB5tUYMgIg+i0chvs1Ex4zkiz5yFKqKzcjiA3oRT2LYqaQcARzh51+wrZg82aapaEiP8rJ5CT++pCNrk0thon+7ZGMkd74dSN90prMkaO4fAko9eNTTX0Q26Rx6UF2NAD19KhCOrb2TfE1UKgmtLMA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=from:to:cc:subject:in-reply-to:references:user-agent:date:message-id:mime-version:content-type:content-transfer-encoding:sender; b=NJHlVeQDY44q61Wa7l3kZdSXbC+egzaRQa5VYibHO0pD9WcCEGmQQyVfcoWI2iCBfxP927qwugFi0laYWZsavUKHzPp/6na6YvbLHvsuPUWFG8JH2FcfTIZ6B4UyREufpj7Spig/O+JbynlZz1m5lj4ZscZ68bikmzkycDJzWnY= Original-Received: by 10.82.105.13 with SMTP id d13mr32424664buc.30.1199570457770; Sat, 05 Jan 2008 14:00:57 -0800 (PST) Original-Received: from bzg.ath.cx ( [81.157.28.72]) by mx.google.com with ESMTPS id d24sm2579346nfh.19.2008.01.05.14.00.55 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 05 Jan 2008 14:00:56 -0800 (PST) Original-Received: by bzg.ath.cx (Postfix, from userid 1000) id B0105157977; Sat, 5 Jan 2008 22:00:53 +0000 (GMT) In-Reply-To: (=?iso-8859-1?Q?=22=D3scar?= Fuentes"'s message of "Sat, 05 Jan 2008 20:05:42 +0100") User-Agent: Gnus/5.110007 (No Gnus v0.7) Emacs/23.0.0 (gnu/linux) X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:86238 Archived-At: Óscar Fuentes writes: > A bug tracker is a dynamic system in the sense that it can take > sophisticated actions in response to its input, and we can exploit this > on a variety of ways. A problem I perceive from the outside is that, for > a casual Emacs contributor, it is too hard to monitor mailing lists > looking for bug reports concerning the module(s) you maintain. The bug > tracker can associate an "owner" for every report. This owner is > determined either by the reporter's choice of affected module (say > cc-mode), or by some overseer that performs a superficial analysis of > the report (such person does not need to know a lot about Emacs > internals, an ignorant like me could do a decent job). The bug tracker > notifies the owner about the new bug and he can query the system for the > bugs assigned to him. > > The advantages of a living database over a static text file are too > large to enumerate. org-mode does pretty well in handling text files *dynamically* from within Emacs. To be more concrete, here is an example of a possible TODO.org file: ======================================================================== * Important bugs * Small bugs ** TODO Fix issue about fontication in picasso-mode DEADLINE: <2008-01-28 lun> :PROPERTIES: :MAINTAINER: pablo@cubism.net :EMAIL: [[http://news.gmane.org/find-root.php?message_id=%3C20080104164454.0A4BD830697%40snark.thyrsus.com%3E]] :FOR_RELEASE: 23.1 :END: This part of the bug item may contain more detailed explanations about the bug. But this is not mandatory. ** INPROGRESS Fix documentation bug for zen-mode :PROPERTIES: :MAINTAINER: confucius@stayaway.org :EMAIL: [[http://news.gmane.org/find-root.php?message_id=%3C22342347.0A4BD830697%40test.server.com%3E]] :FOR_RELEASE: 23.0 :END: * Feature requests ======================================================================== Depending on your needs, you then can look at this file from many different perspectives. You might want to look for entries that are handled by someone specific, or entries that are crucial for the next release, or entries that are currently in the INPROGRESS status... Again, the main advantage here is that this way of handling bug and development issues requires a small amount of work on the top of the actual files in emacs/etc. I guess Using Org would help making Emacs tasks sneak into Emacs developers to-do lists... -- Bastien