On the basis of what is described about statuses (https://bugs.freedesktop.org/page.cgi?id=fields.html#status) I understand that every report starts its life as UNCONFIRMED. Next a power user can "accept" a bug and set the status to NEW. So apparantly there is something seriously wrong in the process control. The group could decide that a bug needs at least one confirmation before it is accepted. I don't know if this is possible to be automated, but as a start all submissions (like the one below) without a comment should be reset to status UUNCONFIRMED. Pieter
> -----Original Message----- > From: Rainer Bielefeld [mailto:[email protected]] > Sent: Sunday, April 17, 2011 8:52 AM > To: [email protected] > Subject: Re: [tdf-discuss] QA - Bug Confirming: Volunteers required > > Steve Edmonds schrieb: > > This is may be where I am confused or misunderstanding. The above > > search returns 17 bugs UNCO, but there are many bugs marked > NEW, such > > as from random *3963* > > <https://bugs.freedesktop.org/show_bug.cgi?id=3963>. This > is NEW and > > there is no indication it is CONFIRMED, therefore I assume > it is UNCONFIRMED but it is not in the search. -- Unsubscribe instructions: E-mail to [email protected] Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.documentfoundation.org/www/discuss/ All messages sent to this list will be publicly archived and cannot be deleted
