Re: bug hunting process report
| From: | Zak Greant | Date: | Fri, 18 Aug 2000 22:56:11 +0000 |
| Subject: | Re: bug hunting process report | ||
| References: | 1 | Groups: | php.qa |
| Request: | Send a blank email to php-qa+get-824@lists.php.net to get a copy of this message | ||
At 12:42 AM 8/19/00 +0200, you wrote:
On Sat, 19 Aug 2000, André Langhorst wrote: Hi all, that´s current statistics open ana sus dup ass feedback 272 75 9 28 17 188 there are quite a lot of old feedback-bugs (4.0.0 and prior) with +20 days of no feedback which should be investigated for closing...That sounds sensible to me. We should also probably contact the developer who put the report into feedback status to see if anything has happened. - zakI think 20 days is way too short. The bug reports don't harm anyone, they often contain useful information.A more sensible system could look like this:1. After one month of being in feedback state, send the submitter a reminder. 2. After two months, close the bug report.The Apache bug db is operated similarly. It can work for us as well.