Subject: Re: [boost] Policy for breaking changes
From: Olaf van der Spek (ml_at_[hidden])
Date: 2017-12-03 09:18:32
On Sat, Dec 2, 2017 at 10:52 PM, Edward Diener via Boost
> If the breaking change is not part of the private API usually you notify
> end-users for at least one Boost release, before making the change in a
> subsequent Boost release. This also includes C++ level requirements.
> If the breaking change is private, then no matter what it is I see that as
> something the maintainer of a library can do at any time.
If it's private, how can it be a breaking change?
> As far as providing major changes to non-private functionality as a whole
> new "release" of the library, then it is up to the maintainer if he wants to
> still provide a backward compatibility layer. But once again, whatever the
> decision, if the end-user has to do something differently to use the library
> as he did before, I think my first paragraph answer should still be in
> Unsubscribe & other changes:
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk