I want to push interest in bug confirming.
Currently we have lots of bugs with status UNOCNFORMED, waiting for
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
before they start.
Some really easy candidates whatr still are "unotcued" are:
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
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
Unsubscribe instructions: E-mail to firstname.lastname@example.org
*** All posts to this list are publicly archived for eternity ***
- [tdf-discuss] QA - Bug Confirming: Volunteers required · Rainer Bielefeld
Impressum (Legal Info)
: 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