On 02/08/2013 07:31 AM, Stephan Bergmann wrote:
The published vs. unpublished is something of a red herring here. The
real issue is if there is a problem you want to fix for a micro release
and the fix requires incompatible changes. The solution is as always,
if the benefits are considered higher than the risks, then make the
incompatible change, otherwise don't (i.e., postpone indefinitely or
postpone until the next minor or even major, where the perceived risk
might be smaller).
Anyway, so I understand your point to be
1) Try to limit API changes to the major releases (4.0, 5.0, 6.0 etc).
2) API changes in minor and micro releases are still considered only if
it's really really necessary. Otherwise, wait until the next major release.
Kohei
--
Kohei Yoshida, LibreOffice hacker, Calc
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.