310209 - Delete the new auto-resolve logic; it is a cop-out and a cover for irresponsibility

Status: RESOLVED INVALID

(bugzilla.mozilla.org :: General, defect)

Description

[John David Galt]

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7

When someone reports a bug or requests an enhancement, it needs to be solved. 
That need doesn't go away just because it is neglected.  The only reason anyone
would want to mark lots of unresolved bugs as resolved is so he/they can falsely
claim to have fixed nearly every problem.  If you are embarassed by the fact
that years-old bugs are around, don't sweep that fact under the rug, just put
out calls for help or provide a forum for bug reporters to do so easily.

Reproducible: Always

Steps to Reproduce:

Comment 1

[timeless]

we wouldn't want this bug to be autoresolved

Comment 2

[Asa Dotzler [:asa]]

What auto-resolve logic? I'm not aware that we're using any Bugzilla
auto-resolve logic. We will be running some scripts we've developed across
bugzilla.mozilla.org to resolve old and unconfirmed bug reports. 

Comment 3

[Jo Hermans]

Note that only *unconfirmed* bugs were marked, bugs that were long ago filed on
old versions. If nobody could confirm it except the original author, why should
it stay open ?

Due to the shortage of people to triage bugs, we have no choice but to ask
people to confirm themselves again, with the latest beta. Otherwise it will take
years before the bug is resolved (most likely duplicated, but it could include
INVALID or WORKSFORME too). The point of these mails is to fish for bugs that
are rela, and the people care about. Even a single reaction from the owner will
prevent them from being resolved automatically.

(before I get an angry remark - I have been triaging bugs for years. And in my
daytime job, we drop bugs when they can't be confirmed in a week.)