Re: bug hunting process report

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? Just stale feedback bugs clutter the field, so that if you just look over the list to see if there's something you can help, these bugs make you to waste time with looking on them and saying "doh, can't do anything with it". -- Stanislav Malyshev stas@zend.com +972-3-6139665 ext.106