From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: =?iso-8859-1?Q?=D3scar_Fuentes?= Newsgroups: gmane.emacs.devel Subject: Re: Why Emacs needs a modern bug tracker Date: Sun, 06 Jan 2008 20:57:00 +0100 Message-ID: <7iimzq0j.fsf@telefonica.net> References: <20080104164454.0A4BD830697@snark.thyrsus.com> <200801041833.37632.andreas.roehler@online.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1199649490 20122 80.91.229.12 (6 Jan 2008 19:58:10 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 6 Jan 2008 19:58:10 +0000 (UTC) Cc: Richard Stallman To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jan 06 20:58:31 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 1JBbdd-0005CZ-FN for ged-emacs-devel@m.gmane.org; Sun, 06 Jan 2008 20:58:29 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JBbdG-0002kO-I1 for ged-emacs-devel@m.gmane.org; Sun, 06 Jan 2008 14:58:06 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JBbcW-0002Av-UE for emacs-devel@gnu.org; Sun, 06 Jan 2008 14:57:21 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JBbcT-00026q-UZ for emacs-devel@gnu.org; Sun, 06 Jan 2008 14:57:20 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JBbcT-00026V-OK for emacs-devel@gnu.org; Sun, 06 Jan 2008 14:57:17 -0500 Original-Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1JBbcT-000086-6l for emacs-devel@gnu.org; Sun, 06 Jan 2008 14:57:17 -0500 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1JBbcL-0000ej-Lz for emacs-devel@gnu.org; Sun, 06 Jan 2008 19:57:09 +0000 Original-Received: from 169.red-81-35-77.dynamicip.rima-tde.net ([81.35.77.169]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 06 Jan 2008 19:57:09 +0000 Original-Received: from ofv by 169.red-81-35-77.dynamicip.rima-tde.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 06 Jan 2008 19:57:09 +0000 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 49 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 169.red-81-35-77.dynamicip.rima-tde.net User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.50 (windows-nt) Cancel-Lock: sha1:66n2CQi8Vv50fq2O0jITCKbuzq0= X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) 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:86376 Archived-At: Richard Stallman writes: > I don't know what ESR plans to do, but speaking from my technical > knowledge about the system I use: people would use email by default for > altering bug reports. You could add comentaries, assign owners, close, > and reopen them. The only requisite is that your e-mail message should > carry a prominent, non-ambiguous command and a reference to the bug > report. This is usually a number plus some marker, such as #1341. > > That sounds ok, so far. Can you show me what a couple of these > messages look like? This would work: Subject: [some-bug-id] Normal subject text Message Body: COMMAND (Optional, if missing the system assumes it's a commentary. A command could be INVALID, WONTFIX, CLOSE, REOPEN, ASSIGN-TO, etc). Normal text body. For instance: ----- Begins e-mail: From: somebody@somewhere.org Subject: #2349 Display corrupted on X. Message Body: CLOSE Just committed a fix and blah, blah, blah. ----- Ends e-mail. That's all. There are quite a few details to consider, depending on the exact policy we want to follow. But overall, the use would be no more complex than the examples above. > Also, what is the name of this bug tracker? We need to think about > which one to use. We can't just rush to enable _any old_ bug tracker. Trac: http://trac.edgewall.org/ It nicely integrates a bug tracker, a browser for the VCS and a Wiki (it does not force you to use everything). -- Oscar