Re: What is our definition of a "Backward Compatibility Break"

2012/9/10 jpauli <jpauli@php.net>: > Based on our recent discussion on #pecl , I'd like we clarify what we > think is a "BCB" (Backward Compatibility Break) as well as what "only > minor BC breaks" could mean. > Stas' recent topic on internals "On BC and interfaces" may serve as a > reflection basis. > As our release process told us that we should not add BCB (but only > "minor" ones ... hum) in any minor release (nor revision), and as 5.5 > release process is going to start soon, I'd like we try to all agree > on that point. > > > What could be qualified as a BCB ? Any modification that change the behaviour of an existing API? Most of libraries change their minor version number when they add a new interface, but they change their major number when an existing interface is modified.