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


Hi Twayne,

Twayne wrote (24-08-11 21:44)
Can we expect there to be a "stop" any time soon in development in order to
attack and destroy some of the bugs and problems?
    Along with that, a bug list of what's being fixed, in process and and
fixed would go a long, long ways. I always read the change lists, but they
don't do a whole lot of good when I'm not familian with that bug, often
because the description is different than the accepted bug description.

Bugzilla and all other info is public.
It is relatively easy to query for bugs, fixed, enhancements etc.

A great page, with many queries predefined, is this one:
http://wiki.documentfoundation.org/BugReport_Details

Other useful info for your help:
http://wiki.documentfoundation.org/BugTriage
http://wiki.documentfoundation.org/BugReport
http://wiki.documentfoundation.org/QA

If you do that yourself, the developers have their hands free to continue fixing bugs, improving build, helping other devs etc. :-)

HTH,

--
 - Cor
 - http://nl.libreoffice.org


--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
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.