Date: Thu, 10 Dec 1998 11:48:41 +0100 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com> Cc: Greg Lehey <grog@lemis.com>, Joseph Koshy <jkoshy@FreeBSD.ORG>, committers@hub.freebsd.org, vanmaren@fast.cs.utah.edu Subject: Re: Swat teams (was: problem reports) Message-ID: <1238.913286921@critter.freebsd.dk> In-Reply-To: Your message of "Thu, 10 Dec 1998 01:19:15 PST." <29693.913281555@zippy.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <29693.913281555@zippy.cdrom.com>, "Jordan K. Hubbard" writes: >> The big thing that many people forget here, though (and it applies at >> least as much to commercial support organiziations) is that the real >> purpose of a PR is to draw attention to a problem. The fact that the > >The problem with this line of thinking is that when there are over >1500 unclosed PRs, many of which are so old that they'll more than >likely never be looked at again, they're not drawing attention to much >more than the fact that there are over 1500 unclosed PRs. Let me chime in here, now that I've woken up. Spending about one hour a day, I was able to keep the numbers of PRs almost steady. This was possible by pretty ruthlessly closing the bogus new ones, and by sweeping through the old ones. I could on average close 50% of the old ones using a criteria of: If version is very old -> close If unreproducible -> close If suspected hardware -> close If mail bounces -> close. Sticking a "[PATCH]" on the synopsis line doesn't seem to have triggered too many committers into action. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1238.913286921>