On Thu, 2011-09-22 at 10:27 -0700, Clint Byrum wrote: > So I'm not sure what you would expect from distros, but please share > and we'll setup automated tests, call for our users to test, whatever > it takes to avoid this type of situation.
This issue is not about packagers specifically. What we need is that more application and library developers test it. I think it is a shame that PEAR, a php.net project like PHP itself, breaks. This must not happen. I have no idea what to do though. We have a list of "primary testers" where I usually get one or two responses but most goes into the void. When talking to application maintainers they don't have the time or similar reasons and hope/trust that others will test enough. Maybe a good thing in all this is that it is wakening ... What else can we do? - More application tests? That's a nice idea but not knowing the applications it is relatively time consuming to analyze test failures in there (not to mention that many projects have a bad test coverage ..) that happen easily due to "unimportant" changes. johannes -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
