From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by monty-python.gnu.org with archive (Exim 4.30) id 1B561z-0002Yo-Ar for mharc-grub-devel@gnu.org; Sun, 21 Mar 2004 11:42:35 -0500 Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30) id 1B561x-0002Y0-A5 for grub-devel@gnu.org; Sun, 21 Mar 2004 11:42:33 -0500 Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30) id 1B561R-0002Pv-II for grub-devel@gnu.org; Sun, 21 Mar 2004 11:42:32 -0500 Received: from [213.228.0.62] (helo=postfix4-1.free.fr) by monty-python.gnu.org with esmtp (Exim 4.30) id 1B561R-0002Pi-93 for grub-devel@gnu.org; Sun, 21 Mar 2004 11:42:01 -0500 Received: from openbrick.enbug.org (boitelle-1-82-66-127-114.fbx.proxad.net [82.66.127.114]) by postfix4-1.free.fr (Postfix) with ESMTP id 85869D6B58 for ; Sun, 21 Mar 2004 17:41:56 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by openbrick.enbug.org (Postfix) with ESMTP id BCE59177500 for ; Sun, 21 Mar 2004 19:42:16 +0100 (CET) From: "Yoshinori K. Okuji" Organization: enbug.org To: The development of GRUB 2 Date: Sun, 21 Mar 2004 17:44:57 +0100 User-Agent: KMail/1.5.3 References: <871xnocv87.fsf@marco.marco-g.com> In-Reply-To: <871xnocv87.fsf@marco.marco-g.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200403211744.57977.okuji@enbug.org> Subject: Re: Bug tracker X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.4 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Mar 2004 16:42:33 -0000 On Friday 19 March 2004 23:44, Marco Gerards wrote: > It seems important to me to use a bugtracker. We talked a bit about > it on IRC, but IIRC there was no outcome (or I forgot). I do not > really care what bugtracker I have to use (I am familiar with the one > on savannah, but I would prefer one with email support). These are from my experience: 1. Once a bug tracker is chosen and used, it is not very easy to migrate to another, because the database cannot be moved (AFAIK, no bug tracker supports this feature), and the URL is recorded in many places, such as an old manual. 2. A bug tracker with rich features looks nice, but it's very difficult to maintain. 3. Integration of e-mail with a bug tracker is really problematic. The main cause of this is that the behavior of MUA varies from MUA to MUA. So I think the oldest method is the best: just having a file named BUGS. If you want to refer to mails related to a bug, you can write a URL of the list archive. If you use YAML as the format, it would be easy to write a helper application for it. What do you think? Okuji