Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index

On the basis of what is described about statuses
( 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.

-----Original Message-----
From: Rainer Bielefeld [] 
Sent: Sunday, April 17, 2011 8:52 AM
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* 
<>. 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
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.