> That is exactly my point. I no more than read the encouraging report that > its been identified and is close to a fix, and the next message says > 4.2 has been released. > > It couldn't have waited just another week to get this fix in and tested?
No, because it wouldn't make much of a difference. There will be other bugs. This is brand new code. Like I said, it will take a couple of months to stabilize. People should not be running Apache2+PHP in production yet. Any why exactly are you focusing on PHP here? Why not complain to the Apache folks about releasing Apache 2 before this was cleared up? This is not likely to be a PHP-specific bug and will require changes on both sides. -Rasmus -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php