> Actually I personnaly don't think 'we cannot declare it stable' leads to > 'we cannot release it'. Why just not say 'Apache 2 support is unstable, > use it on your own risk and only if you know what you are doing'?
As you mentioned, it caused segfaults in mysql. as Derick mentioned, we haven't done any serious QA. as apache mentioned, it's just gone on GA, so there will probably be a bugfix release w/in the next month of bugs complained about on the apache lists. we should forgoe a release that includes apache2 compliancy, and make sure we have a release that is stable. imho. james -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
