BBC: Breaking Backward Compatibility

Hello Justin & QA folks, First I have to admit my aim was not so clear in our last "[PEAR-QA] BC, testing, BBC" discussion... apologies. As I review the exchanges, the point is more Breaking Backward Compatibility (BBC). Again, BBC should never occur, that's the strength of PHP+pear. But PHP+pear is deeply involved in some hot world with the web, technologies ... permanently moving. So as you mentionned, some objectives as security cannot be skipped and must eventually lead to a BBC. It's also sometimes very cruel not to get some better existing functionnality just because BBCs are to be avoid. The way to go over BBC by producing a second package as PHPUnit / PHPUnit2 should be absolutely reserved to major review of the package as here, PHP4-->PHP5. (in this case PHPUnit5 could have been more "talking") Just because a second package can double the maintenance. So, BBC could be admissible in extreme cases. Sure it must be then documented and exampled. Possibly some patches, awk ... to semi-automate scripts' adaptation. More over, as little people read the doc and changelogs, explicit warnings are to be introduced, in the sources, but ALSO during the installation/upgrade. e.g. package "aPckg" was upgraded with a BBC, and install is run: $ pear upgrade aPckg WARNING: due to ... reason, aPckg breaks backward compatibility, so if you use ... feature, take care to adapt your scripts as documented in ... URL Go ahead ? (y/n) : _ If this feature allready exists in pear, how to use it ? à+ bertrand Gugger (toggg)