> after a little discussion on IRC, we came to the conclusion that it is not > a good idea to say that php 4.2.0 supports apache 2. The reasoning behind > is that we are not even 50% sure if apache 2(.0.35) works correctly, or > that the filter works correctly. This is because no single QA was done on > it and we wont be able to do that before the release. I do not want to > postpone the release because the apache dudes released their new workhorse > on a very short notice while rushing it to release. I am not confident > that apache 2 / PHP 4.2.0 is stable enough for production yet, and > therefore recommend to drop the apache2filter from the release branch. "If > you can't do it properly, don't do it" is my motto here. I hope this is > the same with you.
I definitely agree that we need to make sure that we do not release a version we consider stable and have it crashing due to the apache 2 stuff. we shouldn't be bullied into releasing this as it's clear that our support hasn't been finalised yet. James -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
