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


We are all receiving the daily Libreoffice-bugs Digests and I, and no
doubt many others, would like to know how all the bugs listed in the
Digests are monitored and acted upon.

It looks as if we have an ever growing list of bugs of all
complexities, from the serious "show stoppers" to the exotic, "once in
a lifetime bug" only found by people doing very advanced work.  But
where is the feed-back to show that problems raised are being
resolved?  Who takes ownership of a given bug after it has been reported?

How are these issues managed by the Libre Office team?

Alan


The bug reporting process will give you a few hints until someone
involved on the dev side of things can respond:
http://wiki.documentfoundation.org/BugReport

Adding yourself as a "CC" to some of the bugs you mention may also give
you a "history may repeat itself" view of things.

Cheers,

Fabian

--
LibreOffice questions ? Des questions sur LibreOffice ? Preguntas acerca
de LibreOffice ? Ask LibreOffice: http://libreoffice.shapado.com/
~
Fabián Rodríguez
http://wiki.documentfoundation.org/User:MagicFab


-- 
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.