If you want to reason why things were done was they were just check the archive. All your arguments have been brought up before. Apparently a decision was made (that does not match your perception).
Best regards, Lukas Smith [EMAIL PROTECTED] _______________________________ DybNet Internet Solutions GbR Reuchlinstr. 10-11 Gebäude 4 1.OG Raum 6 (4.1.6) 10553 Berlin Germany Tel. : +49 30 83 22 50 00 Fax : +49 30 83 22 50 07 www.dybnet.de [EMAIL PROTECTED] _______________________________ > -----Original Message----- > From: Brian Foddy [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, April 23, 2002 7:44 AM > To: Rasmus Lerdorf > Cc: PHP Developers Mailing List > Subject: Re: [PHP-DEV] PHP 4.2.0 Release Announcement > > On Mon, 22 Apr 2002 18:56:28 -0700 (PDT), Rasmus Lerdorf wrote: > > >> As for Apache being at fault too, they very well could be. But the > >> fact remains that PHP runs INSIDE Apache, and Apache starts fine > without > >> PHP, hence PHP must be at fault. Simply stating the obvious facts from > >> the public point of view. > > > >Well, with that sort of logic we are completely screwed and might as well > >just give up. > > > >Public perception ranks very low on the priority list. 99.8% of users > >couldn't care less about Apache2 at this point. PHP 4.2 has been slow > >enough in coming. Holding it up longer for the .2% of users it might > >affect makes no sense. Those users can experiment with the snapshot > >releases. > > > >-Rasmus > > > Ultimately, I'm just trying to look out for other PHP users, > not me. People who > don't follow these mailing lists. They see on the net that a new > improved Apache is released. They check the PHP web site/freshmeat > and see a new version that claims support for Apache, experimental > tho it may be. > > So they download both and start building. What do they get? > Core dump. Usually before people will start opening trouble > records or searching bug databases people will spend several > hours re-rebuilding, double checking proceedures, etc, etc, etc. > They've done everything correct. Its supposed to work, says right > on the web page. Why does this core dump? > > They finally open a bug report only to have it immediately reply > with... "Yes, we know. What we really meant by 'Experimental' > was it will core dump". That doesn't sound very good. > > That's a very frustrating scenario that will be occuring countless > times probably right now. Why does PHP want to intentionally > frustrate and turn off its own user community? What does > that say about the PHP testing process and commitment to users? > > Now that 4.2 has been released and announced, the horse has left > the barn. The only thing we can really do now is at least put a > new note clearly on the web page stating that there is this problem > with these two latest releases. "Experimental, not for production" > just doesn't cut it. Not when we KNOW there is a definate problem, > not some potential bug you might encounter. > > I've said my peace, > Good night. > Brian > > > > -- > PHP Development Mailing List <http://www.php.net/> > To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
