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

Uwe Altmann wrote:
It should be possible from my point of view that some devs take
the responsibility to check new code to avoid api-breaks. And put
to the conscience of all devs that it should be a top priority to
avoid breaking the API-compatibility (no matter if they are made
in OOO or LO).

Hi Uwe, all,

breaking API has, and will happen everytime code is changed. It
happened for OOo, despite a much more heavy-weight development
process, and it will happen in future.

But there's a remedy - every extension author who's interested in
having his extension working is heavily encouraged to test it with
our nightly builds every once in a while:

and flag every problem, preferrably with a well-researched bug
report - and even more preferrably show up on our dev list to help
isolate the problem. :)


-- Thorsten

Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.