On Fri, Nov 25, 2016 at 12:02:03PM +0100, Michael Stahl wrote:
since the goal of the policy is "we can make incompatible changes
whenever it doesn't affect any 3rd party extension or macro", the
"published" tag is much less useful as guidance than it may appear at
first glance.
So, uhmm, if the current/old use of "published" doesnt service core developers
and doesnt serve UNO users, maybe we should consider making it useful? A
radical step would be to remove the "published" tag everywhere (as we allow
ourselves API changes anywhere already) and then carefully readd them in areas
where we are reasonably sure we dont have to break the API again soon.
Best,
Bjoern
Context
Firebird 3 by default [was: minutes of ESC call ...] · Lionel Elie Mamane
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.