From mboxrd@z Thu Jan  1 00:00:00 1970
Path: main.gmane.org!not-for-mail
From: Richard Stallman <rms@gnu.org>
Newsgroups: gmane.emacs.devel
Subject: Re: Bug tracking (was: new *Help* argument highlighting)
Date: Fri, 11 Jun 2004 21:50:59 -0400
Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org
Message-ID: <E1BYxff-0007QJ-2d@fencepost.gnu.org>
References: <20040512103042.FB57.JMBARRANQUERO@wke.es>
	<E1BOIOq-0007s3-U0@fencepost.gnu.org>
	<20040611122633.5F88.JMBARRANQUERO@wke.es>
Reply-To: rms@gnu.org
NNTP-Posting-Host: deer.gmane.org
X-Trace: sea.gmane.org 1087005163 29403 80.91.224.253 (12 Jun 2004 01:52:43 GMT)
X-Complaints-To: usenet@sea.gmane.org
NNTP-Posting-Date: Sat, 12 Jun 2004 01:52:43 +0000 (UTC)
Cc: emacs-devel@gnu.org
Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Sat Jun 12 03:52:39 2004
Return-path: <emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org>
Original-Received: from quimby.gnus.org ([80.91.224.244])
	by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian))
	id 1BYxhH-0001aJ-00
	for <emacs-devel@deer.gmane.org>; Sat, 12 Jun 2004 03: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 1BYxhG-0006bw-00
	for <emacs-devel@quimby.gnus.org>; Sat, 12 Jun 2004 03:52:39 +0200
Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.33)
	id 1BYxi2-0004Fa-Gq
	for emacs-devel@quimby.gnus.org; Fri, 11 Jun 2004 21:53:26 -0400
Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33)
	id 1BYxgg-0003Q9-7S
	for emacs-devel@gnu.org; Fri, 11 Jun 2004 21:52:02 -0400
Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33)
	id 1BYxgb-0003Nw-NP
	for emacs-devel@gnu.org; Fri, 11 Jun 2004 21:51:58 -0400
Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.33) id 1BYxgb-0003Nt-Km
	for emacs-devel@gnu.org; Fri, 11 Jun 2004 21:51:57 -0400
Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org)
	by monty-python.gnu.org with esmtp (Exim 4.34) id 1BYxff-0001sW-FT
	for emacs-devel@gnu.org; Fri, 11 Jun 2004 21:50:59 -0400
Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34)
	id 1BYxff-0007QJ-2d; Fri, 11 Jun 2004 21:50:59 -0400
Original-To: Juanma Barranquero <jmbarranquero@wke.es>
In-reply-to: <20040611122633.5F88.JMBARRANQUERO@wke.es> (message from Juanma
	Barranquero on Fri, 11 Jun 2004 12:53:47 +0200)
X-BeenThere: emacs-devel@gnu.org
X-Mailman-Version: 2.1.4
Precedence: list
List-Id: "Emacs development discussions." <emacs-devel.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/emacs-devel>
List-Post: <mailto:emacs-devel@gnu.org>
List-Help: <mailto:emacs-devel-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=subscribe>
Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org
Xref: main.gmane.org gmane.emacs.devel:24854
X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:24854

    Still, the question remains: should we use some kind of issue tracker?

It would be useful to keep track of the problems that need to be
solved before we can make a release.  However, using some special
"issue tracker" seems like doing it the hard way.  All we need
is a file we can edit.  We can keep it in /etc using CVS and edit
it with Emacs.

The main job is collecting the information to put in the file.