From owner-cvs-all Sat Dec 12 20:28:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA09464 for cvs-all-outgoing; Sat, 12 Dec 1998 20:28:10 -0800 (PST) (envelope-from owner-cvs-all@FreeBSD.ORG) Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA09459 for ; Sat, 12 Dec 1998 20:28:08 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with SMTP id WAA32334; Sat, 12 Dec 1998 22:28:02 -0600 (CST) Date: Sat, 12 Dec 1998 22:28:02 -0600 (CST) From: Steve Price To: Matthew Dillon cc: cvs-committers@FreeBSD.ORG Subject: Re: gnats database - what to do w/ 2.2.x bug reports? In-Reply-To: <199812130112.RAA13759@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk For what it's worth, I've found that sending out what amounts to a chain letter, asking if the problem exists, have you tried a newer version, etc. is about all that is required to close most of the ones that you are talking about. Taking them out of the limelight (the open state) will have exactly the opposite of the desired effect - they will become even more forgotten. In your own words - "so I don't keep on going over them". It is not that you should keep going over them, but rather that we want them resolved. Moving them to an even darker corner of the closet won't help much I'm afraid if fixing the problem is the ultimate goal. Although if you feel compelled to move them to another state, I'd vote for feedback, with the appropriate "does the problem still exist?" letter being sent in conjunction with the change. I did it a couple of nights ago and within a two hour timeframe I was able to close over 20 PRs without a single commit. YMMV. -steve On Sat, 12 Dec 1998, Matthew Dillon wrote: # I've been browsing the bugs database and there are a whole bunch of # 2.2.x related bugs that I suspect are either fixed or -current or # probably fixed in -current. # # I would like to categorize these bugs so I don't keep on going over # them. Can I move these bugs into a 'suspended' state or can we create # a new 'depreciated' state or something to categorize these bugs ? It # would make management of gnats a bit easier. # # -Matt # # Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet # Communications & God knows what else. # (Please include original email in any response) # To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message