21 Nov
2008
21 Nov
'08
3:56 p.m.
Interface-breaking changes in a specific library are likely to be missed, so *if* we want interface compatibility in some form, we need some other mechanism > in place, for example:
* A policy that interface breakage need to be discussed * Running old release tests against new Boost version * Dot releases
I think I would add another, stronger point: Completely changing the (documented!) behaviour of a component is not allowed in a single release.