Unpublishing API post 4.0

[Kohei Yoshida]

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