From: "J. Bruce Fields" <bfields@fieldses.org>
Subject: Re: [Storage_sig] Re: Question on bug tracking for NFSv4 work
Date: Thu, 9 Dec 2004 17:08:52 -0500
Message-ID: <20041209220852.GD22994@fieldses.org>
References: <200412091441.PAA173944@isatis.frec.bull.fr> <Pine.LNX.4.33.0412091330180.8023-100000@osdlab.pdx.osdl.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Tony Reix <Tony.Reix@bull.net>, hch@infradead.org,
	nfs@lists.sourceforge.net, storage_sig@osdl.org
Return-path: <nfs-admin@lists.sourceforge.net>
Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.11] helo=sc8-sf-mx1.sourceforge.net)
	by sc8-sf-list2.sourceforge.net with esmtp (Exim 4.30)
	id 1CcWSw-0003ZW-Gf
	for nfs@lists.sourceforge.net; Thu, 09 Dec 2004 14:08:50 -0800
Received: from dsl093-002-214.det1.dsl.speakeasy.net ([66.93.2.214] helo=pickle.fieldses.org)
	by sc8-sf-mx1.sourceforge.net with esmtp (TLSv1:RC4-SHA:128)
	(Exim 4.41)
	id 1CcWSv-0003Yg-Ma
	for nfs@lists.sourceforge.net; Thu, 09 Dec 2004 14:08:50 -0800
To: Bryce Harrington <bryce@osdl.org>
In-Reply-To: <Pine.LNX.4.33.0412091330180.8023-100000@osdlab.pdx.osdl.net>
Sender: nfs-admin@lists.sourceforge.net
Errors-To: nfs-admin@lists.sourceforge.net
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/nfs>,
	<mailto:nfs-request@lists.sourceforge.net?subject=unsubscribe>
List-Id: Discussion of NFS under Linux development,
	interoperability,
	and testing. <nfs.lists.sourceforge.net>
List-Post: <mailto:nfs@lists.sourceforge.net>
List-Help: <mailto:nfs-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/nfs>,
	<mailto:nfs-request@lists.sourceforge.net?subject=subscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=nfs>

On Thu, Dec 09, 2004 at 01:53:53PM -0800, Bryce Harrington wrote:
> Maybe a good compromise would be for those of us doing testing who
> want to track bugs, to do so, but continue using the mailing lists as
> the primary mechanism.  That way if the bug tracking approach fizzles
> out, it doesn't affect normal processes, but if it succeeds then
> people can make heavier use of it.  Does this sound like a feasible
> approach?

I think that's the only way to go.  Some developers may just never look
at the bug database, so it may be necessary for other people to do
things like retest and close old bugs for them.

A bug database is certainly worth a try, though.

--b.


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs