Hi,
On Thu, Nov 24, 2016 at 07:02:17PM +0000, Michael Meeks wrote:
Personally I think Markus' take - that we shouldn't be using UNO API
for this internal stuff is spot-on - push the API problem to the edge:
but others have different views =)
FWIW, up to this point we made no distiction between how we handle published
and unpublished interfaces. Maybe now that we have had some cleaning up
published interfaces, it might be the time to reconsider making the barrier to
API break between those two more explicit[1].
Just a thought -- while I know that we (well, OpenOffice) initially
overpublished APIs, I dont know if we handled it more sensible since then, if
there is any value at all in the "published" tag again at this point.
@Stephan: Thoughts?
Best,
Bjoern
[1] And I dont mean "you shall never break published, but you can break the
world in unpublished" -- but in more nuanced shades.
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.