Re: Re: BBC: Breaking Backward Compatibility

Justin Patrin wrote:

On Sun, 21 Nov 2004 13:31:35 +0100, bertrand Gugger <bertrand@toggg.com> wrote:

Hello Justin & QA folks, <skip>

Sorry Bertrand, but this has been discussed extensively already. The major version update is there for many reasons that have already been debated, not the least of which is that people often upgrade without thinking and end up with unusable scripts. Furthermore many people use other people's code and if upgrading PEAR breaks that code they may not be able to fix it. If updating a package makes lots of BC breaks, then it either hasn't been architected right or should still be unstable. I absolutly agree, Justin,

as pear is quite distributed as php so far and anywhere, no break more allowed then should every architecture the best in mood should every acceptance of a new component control its architecture what I agree again. so review that vote system. Anyway, is it possible to instruct pear to make some warning or confirm by "upgrade" ? best, bertrand