Re: Bugzilla bug tracking database for 2.5 now available.

[Arnaldo Carvalho de Melo <acme@conectiva.com.br>]

Em Sat, Nov 16, 2002 at 01:44:19PM -0800, Martin J. Bligh escreveu:
> >> Very bad idea. People using unusual hardware do not want to keep
> >> re-submitting a bug report. I know when I submit a report I expect 
> >> that it will remain until the problem is fixed. I do not like to 
> >> receive multiple
> > 
> > Oh well, there is _no_ guarantee that it will be fixed, sometimes 
> > there is no  maintainer at all and the ticket will stay there forever 
> > lost in the noise...
> > And if anybody is interested in fixing the driver or even looking to 
> > see if somebody submitted a ticket he/she can just search for all 
> > tickets, even the ones closed because nobody is did any activity in 
> > a perior of one month (or any other timeout period).
> > 
> > Its not like the ticket will vanish from the database.
 
> One thing we've done before in other bug-tracking systems was to create
> a "STALE" state (or something similar) for this type of bug. So it 
> wouldn't get closed (I have seen this done as a closing resolution, but
> I think that's a bad idea), but it wouldn't be in the default searches
> either ... you could just select it if you wanted it ... does that sound
> sane? (obviously we don't need this yet, but might be a good plan
> longer-term).

looks sane, the idea is that automatically bugzilla would move things that
didn't had any activity to a state that doesn't appears on the default
searches, this can help with dups as well, only the most recent duplicates
would, over time, appear on the default searches. And the others would
remain in STALE mode forever. STALE for over a year? CLOSED STALE. 8) And
even then it would be in the database...

- Arnaldo