http://qa.mandrakesoft.com/show_bug.cgi?id=5757
------- Additional Comments From [EMAIL PROTECTED] 2003-17-09 03:31 ------- I like the information provided through bugzilla I've seen for some bugs : No activity has been seen on this bug since 20030203 and it is still in UNCONFIRMED state. This probably means that the information provided was not clear enough, or that the bug is not valid anymore. Please test and confirm that this bug is still valid with the latest cooker version, or close it. (225 bugs concerned) maybe add a new status : outofdate ? closing is up to the user which is a good thing to be kept, but if the user is not reliable, stats should not be pessimistic or alarmist. outofdate resembles a garbage collector, keeping only relevant bugs (the user could re-open the bug if needed). -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: launching http://qa.mandrakesoft.com/reports.cgi?product=-All-&datasets=NEW%3A&datasets=ASSIGNED%3A&datasets=NEEDINFO%3A&datasets=REOPENED%3A&datasets=UNCONFIRMED%3A&datasets=VERIFIED%3A&datasets=CLOSED%3A&datasets=INVALID%3A&datasets=WONTFIX%3A&datasets=LATER%3A&datasets=REMIND%3A&datasets=DUPLICATE%3A&datasets=WORKSFORME%3A&datasets=MOVED%3A gives too many unconfirmed bugs (over 1200), I've excluded RESOLVED and FIXED that's not as near to 40000 or 80000 for another os, nevertheless it would seem good will on your part, either to - change to NEEDINFO if bug seems valid in some condition that need to be reproduced, ask for testers with the same configuration if you have not the same configuration (hardware) to reproduce - change to WORKSFORME if cannot be reproduced in newer version with identified configuration - WONTFIX for bugs outside Mandrake's scope (non free) >From a user point of view, UNCONFIRMED means the bug is not taken into account (with no reaseon displayed). That's just a suggestion, maybe worth 10 men-day to be tackled with, deep freeze being a relevant situation to clarify bugs if you want to make a hit with 9.2 (on a good way IMHO). rc3 may be delayed a bit, what the heck if community adheres and new users appreciate the effort !? (even stakeholders who love rating by numbers). Let's expect a 33% decrease (400 more bugs in a good status, rather than unconfirmed). What do you think of it ?
