On 02/08/2013 06:01 PM, Kohei Yoshida wrote:
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.
I would weaken that to just one "really" for minor releases.
(Also, considering just major and minor releases, we do not have the
mismatch problem between lexicographical order of release numbers and
chronological order of releases. At least that is my understanding of
how we plan releases.)
Stephan
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.