Re: BC breaks: Cache_Lite, PHP_Documentor

> This is explicitly prohibited by PEAR standards [1]. A user may miss > the BC break notice, and find their code unexpectedly broken after > upgrading a stable package. People should not be using PHP4 still, but > unfortunately some are and we can't break things for them. > > I think this gets back to the unresolved discussion previously brought > up about old packages [2]. I like the "middle ground" idea Daniel > proposes, but as Helgi notes changing package channels is currently > not supported, so maybe we can find some other solution that still > allows us to move away from PHP4. Some PEAR usage stats on PHP > versions would definitely be useful to see. > > [1] > http://pear.php.net/manual/en/rfc.version-naming.standard.php > [2] http://marc.info/?l=pear-dev&m=127280685832232&w=2 > > Yeah, no one else seemed to care enough at the time for me to tinker around with it, but it might be worth a look.