Hey Andi > My point was that this has nothing to do with Zend or not Zend. My point is not that someone from Zend broke it, but that someone from Zend blamed the community that THEY failed to find the problem. I thought Zend is enough into PHP to test their own products against RC's, too. It makes me angry that in the last months again and again people who earn their money with PHP come and insult those who work on PHP for free and do all the hard work. > It's happened to all of us in the past (except for maybe you) where we > have commited code that had problems. Hehe... I also commited code that cause problems in a release... Like a very slow unserialize() in 4.3.??. And yes I tested it back then but unfortunately that bug only was causing problems were large quantities of data had to be unserialized.
> So people screw up. I prefer having the occasional screw up then less > people helping out. Yeah. But maybe we should setup some rules what exactly we should do when there is a broken tarball or missing files. While it seems nice to just repackage and silently change it (or change it with a warning), it is considered bad practice and is especially bad for people using distributions like Gentoo or the BSD ports system. Even if we don't change the version number we could rename the tarball to php-5.1.4-repack-1.tar.bz2 or something alike. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
