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


Hi,
A question to the developers, which will inevitably become more
important as things push on with LibO and the code base starts to separate :

- what is the current approach, with regard to bug triaging, to bugs
caused by the OOo code base ?

What I mean is that do we consider them to be our own bugs, or not ?

From the bug triager's point of view, it is easy to tell someone that
this is "NOTOURBUG", however, I have my doubts about that because
ultimately, someone who knows nothing about OOo and who has only ever
used LibO, is not likely to understand the underpinning between the code
bases and therefore not be entirely satisfied with the bug being
classified as someone else's when in fact substantially the same code
base is used. Of course, there are people who file reports knowing that
the bug exists in the OOo codebase and hoping that the LibO devs will
sort it out - this is a kind of catch 22 for the bug triager ? - to
clear out or not to clear out ?


I would appreciate your thoughts on the matter, as it will help me to
better sort through the bug reports.


Alex


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.