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


How was the session on triage. I suggest a latest working release
instead of a beta, I cannot afford my LO not to work as I need it every
day and are unsure if I can install a beta and a release copy at the
same time. I do not want to take the risk.

I have been confirming some bugs, but the process is not clear. The wiki
page http://wiki.documentfoundation.org/BugTriage says to add a comment
to state confirmed. There is no way to search for unconfirmed. The
status can not be changed to unconfirmed or confirmed or VERIFIED. The
keywords cannot be set CONFIRMED. The bugs list does not show the
whiteboard (where CONFIRMED can be entered). A report can be done but it
is a work around.

Can the bugzilla be adjusted to help people wanting to confirm bugs and
move them on to the next stage, I suggest the easiest is to fix the
status list.
steve

On 11/03/11 22:43, Rainer Bielefeld wrote:
Hi,

I want to push interest in bug confirming.
Currently we have lots of bugs with status UNOCNFORMED, waiting for
confirmation:

<https://bugs.freedesktop.org/buglist.cgi?query_format=advanced&bug_status=UNCONFIRMED&product=LibreOffice>


And even more important: many NEW bugs also are still unocnfirmed,
have lousy rare descriptions how to reproduce the problem, ...

Bug confirming is really easy, required qualification only is:
- some training using LibO
- a computer, of course,
- some knowledge in English language to understand the reports
- A Bugzilla account.

Newcomers should read hints on
 <http://wiki.documentfoundation.org/BugReport>
before they start.

Some really easy candidates whatr still are "unotcued" are:
<https://bugs.freedesktop.org/show_bug.cgi?id=31856>
<https://bugs.freedesktop.org/show_bug.cgi?id=33636>
<https://bugs.freedesktop.org/show_bug.cgi?id=33978>
<https://bugs.freedesktop.org/show_bug.cgi?id=34093>
<https://bugs.freedesktop.org/show_bug.cgi?id=34121>

Most important goal is a simple and clear statement whether it has
been possible to reproduce the problem. Operating the "Bugzilla
Dahboard" can be done by experienced QA staff.

If you want you may add me to CC list with
<LibreOffice@bielefeldundbuss.de>

I will check your results and initiate all further steps.

Bug confirming is a really important issue, so please be courageous
and try whether oyu can help. Currently our developers still have to
spend too much time with checking bug reports, what will lack for
improving code.

Thanks a lot, and good luck

Rainer Bielefeld


-- 
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
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

Context


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.