From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 8 15:02:15 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A6AEA16A4CE for ; Thu, 8 Jan 2004 15:02:15 -0800 (PST) Received: from shaft.techsupport.co.uk (shaft.techsupport.co.uk [212.250.77.214]) by mx1.FreeBSD.org (Postfix) with ESMTP id 987F243D6B for ; Thu, 8 Jan 2004 15:02:05 -0800 (PST) (envelope-from setantae@submonkey.net) Received: from cpc2-cdif3-6-0-cust204.cdif.cable.ntl.com ([81.103.67.204] helo=shrike.submonkey.net ident=mailnull) by shaft.techsupport.co.uk with esmtp (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.24; FreeBSD) id 1AejAC-000GtY-0P; Thu, 08 Jan 2004 23:02:04 +0000 Received: from setantae by shrike.submonkey.net with local (Exim 4.30; FreeBSD) id 1AejA6-000O95-9J; Thu, 08 Jan 2004 23:01:58 +0000 Date: Thu, 8 Jan 2004 23:01:58 +0000 From: Ceri Davies To: Paul Robinson Message-ID: <20040108230158.GD8322@submonkey.net> Mail-Followup-To: Ceri Davies , Paul Robinson , freebsd-hackers@freebsd.org References: <3FFDDF09.80205@iconoplex.co.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6FinHCQBQ0zFDOqT" Content-Disposition: inline In-Reply-To: <3FFDDF09.80205@iconoplex.co.uk> X-PGP: finger ceri@FreeBSD.org User-Agent: Mutt/1.5.4i Sender: Ceri Davies cc: freebsd-hackers@freebsd.org Subject: Re: A way to clean up PRs? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jan 2004 23:02:15 -0000 --6FinHCQBQ0zFDOqT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 08, 2004 at 10:51:53PM +0000, Paul Robinson wrote: > Just a thought: >=20 > How about everything that hasn't been touched in 3 years gets put into a= =20 > special state of "closed-believed-dead", everything over 12 months (or=20 > 6?) gets the same AFTER an e-mail has been sent out to the originator to= =20 > see if the problem still exists? >=20 > It's just that way, I think a lot of PRs for obsolete hardware and=20 > versions will get closed up, thereby making it easier for those of us=20 > trying to pick our way through and see what is still new and relevant=20 > and in need of some love and care and attention. If somebody still has=20 > the problem and it's an issue, it just gets a new PR that comes back on= =20 > the top of the queue, it's live and we can deal with PRs as they come in. >=20 > Thoughts? Just a thought that might help clean up the DB on an idle=20 > Thursday evening. I'm sure it's been thought of before. Well, here's a extract from a mail I sent to another non-committer interested in doing the same thing, about two days ago. Note that we do already timeout PRs in feedback after a period of time without a reply (currently 3 months). Also note that there's a bugbusters@ list where this kind of discussion should live, but I think I may be the only person subscribed (although rousing the list is really my responsibility, I've yet to think up a good enough scheme). Forwarded mail: Thanks for the offer of help. =09 Sending stuff to current could be considered useful, but committers interested in fixing bugs (which is hopefully all of them!) will all be subscribed to freebsd-bugs@, which means that by simply submitting a followup to the PR they'll get automatically notified. =09 There a few ways for non-committers to help out though: if you think that a PR can be closed, then submit a followup to the PR with the reason why, and include the string "This PR can be closed". The reason can be anything from "this isn't a problem on later releases", "this was fixed in revision x of src/foo/bar/quux.c" to "the user is at fault". =09 Just because a PR can't be closed though, if you have information to add to a PR (an updated patch, "cannot replicate here", etc.) then send it in as a followup. Of course, if you know of (or can code) a fix, send it! Ceri --=20 --6FinHCQBQ0zFDOqT Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQE//eFmocfcwTS3JF8RAo0mAKC0u86BqAdzGBdcpmkytk93Ni4mbgCeMVrq 9ndGy7VU0ZLqBgHsZiFdSyQ= =zeA6 -----END PGP SIGNATURE----- --6FinHCQBQ0zFDOqT--