Re: bug hunting process report
| From: | Sascha Schumann | Date: | Fri, 18 Aug 2000 22:51:49 +0000 |
| Subject: | Re: bug hunting process report | ||
| References: | 1 | Groups: | php.qa |
| Request: | Send a blank email to php-qa+get-822@lists.php.net to get a copy of this message | ||
On Sat, 19 Aug 2000, Stanislav Malyshev wrote:
> SS>> A more sensible system could look like this:
> SS>>
> SS>> 1. After one month of being in feedback state, send the
> SS>> submitter a reminder.
>
> In most cases, if there's not anough info to indetify the problem (like
> "PHP crashes" without reproducing script and backtrace) and user doesn't
> answer for a month, it means either the problem got fixed or the user
> doesn't care for it anymore. Since we have no way to know what was the
> real problem, we might close this as well. There's no information loss -
> the bug is still in the DB, right?
We are talking about a general rule, not about the "foo does
not work. end." bug reports.
If real bug reports are closed after 20 days just because
noone has answerered in that time frame, it is loss of
information. Or when was the last time you looked through the
closed bug reports?
- Sascha