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


I have an even blunter suggestion: In a branch (branched off 5.2, for
instance), we unpublish and rename all existing API. (For instance,
s/com::sun::star/libreoffice/.) We make this very public, and make a test
build available that contains it. And then we wait for reports what
external software actually breaks against this test build. As such reports
come in, we rename back those APIs, and mark them published. Once a week we
distribute a new build from that branch. If after half a year no new
complaints arrive, we know what APIs actively used and/or developed
external software actually uses, and do the corresponding change also in
master.

Of course I don't really believe this suggestion has any chance of being
accepted. But it is Friday, and one can dream.

--tml

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.