Re: [PHP-DEV] PHP 4.2.0 Release Announcement

2002-04-22 Thread Brian Foddy
Have you people lost it??? One of the MAJOR features is working with Apache2. But bug 16475 is still open and unresolved. Its been reported by several different people, all having the same effect. Why would you release this version until after this bug is closed and gone through at least one RC

Re: [PHP-DEV] PHP 4.2.0 Release Announcement

2002-04-22 Thread Rasmus Lerdorf
Apache 2 was released extremely quickly during the PHP 4.2 QA cycle. There really is no huge motivation to switch to Apache 2 right now. If the perchild mpm ever becomes stable it will be cool to use Apache 2 with PHP, but right now you are going to run into a whole lot of trouble with non-thread

Re: [PHP-DEV] PHP 4.2.0 Release Announcement

2002-04-22 Thread Jani Taskinen
FYI: The apache2 support in PHP is new and experimental. And in that bug report, one of the apache developers has already added a note that he's working on it so the fix will be in the next release. (PHP 4.2.1) Patience, please. --Jani On Mon, 22 Apr 2002,

Re: [PHP-DEV] PHP 4.2.0 Release Announcement

2002-04-22 Thread Cliff Woolley
On Tue, 23 Apr 2002, Jani Taskinen wrote: > FYI: The apache2 support in PHP is new and experimental. > And in that bug report, one of the apache developers has > already added a note that he's working on it so the > fix will be in the next release. (PHP 4.2.1) > Patience, plea

Re: [PHP-DEV] PHP 4.2.0 Release Announcement

2002-04-22 Thread Brian Foddy
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? Looking at the 4.2 announcement on the web page states..

Re: [PHP-DEV] PHP 4.2.0 Release Announcement

2002-04-22 Thread Rasmus Lerdorf
> 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 differen

Re: [PHP-DEV] PHP 4.2.0 Release Announcement

2002-04-22 Thread Brian Foddy
Personally, I completely understand that is all new code and bugs will occur. I won't be going to Apache 2 for some time to come. The only reason I even tried it at all is I already was already getting requests on php-tuxedo for that combo so I thought I should give it a try. But I hope the Bug

Re: [PHP-DEV] PHP 4.2.0 Release Announcement

2002-04-22 Thread Rasmus Lerdorf
> 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 sc

Re: [PHP-DEV] PHP 4.2.0 Release Announcement

2002-04-22 Thread derick
On Mon, 22 Apr 2002, Brian Foddy wrote: > 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? Becau

Re: [PHP-DEV] PHP 4.2.0 Release Announcement

2002-04-22 Thread Brian Foddy
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 publ

Re: [PHP-DEV] PHP 4.2.0 Release Announcement

2002-04-22 Thread Dave Mertens
On Tue, Apr 23, 2002 at 12:44:17AM -0500, Brian Foddy wrote: > 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 P

RE: [PHP-DEV] PHP 4.2.0 Release Announcement

2002-04-22 Thread Lukas Smith
: 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

Re: [PHP-DEV] PHP 4.2.0 Release Announcement

2002-04-23 Thread Tom Howell-Cintron
On Tue, 23 Apr 2002, Brian Foddy wrote: > 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 use

Re: [PHP-DEV] PHP 4.2.0 Release Announcement

2002-04-23 Thread Dan Hardiker
I disagree whole heartedly. It doesnt look bad at all. >From the public angle, it looks like the PHP Group are holding back on Apache 2 support until they can endorse its stability - but giving the PHP developers access to current research into the integration. If you want to play with with Apac

Re: [PHP-DEV] PHP 4.2.0 Release Announcement

2002-04-23 Thread Rasmus Lerdorf
You make it sound like it will core dump immediately for everyone. That's obviously not the case. It does work for most people. Well, for some anyway. Works fine on my test server, for example. On Tue, 23 Apr 2002, Brian Foddy wrote: > So they download both and start building. What do they g

RE: [PHP-DEV] PHP 4.2.0 Release Announcement

2002-04-23 Thread Rose, Billy
PHP Developers Mailing List > Subject: Re: [PHP-DEV] PHP 4.2.0 Release Announcement > > > You make it sound like it will core dump immediately for > everyone. That's > obviously not the case. It does work for most people. Well, for some > anyway. Works fine on my test

RE: [PHP-DEV] PHP 4.2.0 Release Announcement

2002-04-23 Thread Rose, Billy
]] > > Sent: Tuesday, April 23, 2002 5:06 AM > > To: Brian Foddy > > Cc: PHP Developers Mailing List > > Subject: Re: [PHP-DEV] PHP 4.2.0 Release Announcement > > > > > > You make it sound like it will core dump immediately for > > everyone. That&#x

Re: [PHP-DEV] PHP 4.2.0 Release Announcement

2002-04-23 Thread Zeev Suraski
At 05:30 23/04/2002, Brian Foddy wrote: >Experimental kinda implies that its at least usuable and might be >fun to play with. Not recommending for production is a long ways >from saying ohh, I guess it will coredump on startup... Experimental means experimental, and that it may very well crash o

Re: [PHP-DEV] PHP 4.2.0 Release Announcement

2002-04-23 Thread Mats Lindh
- [EMAIL PROTECTED]% (Brian Foddy): > So they download both and start building. What do they get? > Core dump. Usually before people will start opening trouble [cut] > with these two latest releases. "Experimental, not for production" > just doesn't cut it. Not when we KNOW there is a definat

Re: [PHP-DEV] PHP 4.2.0 Release Announcement

2002-04-23 Thread Aaron Bannert
> It didn't coredump for me on startup. Nor for I, and I've done quite a lot of testing on this thing. The startup error has been identified (even though not reproduceable by me for some reason) and I will supply a patch for that later today. There is still another bug (also nonreproduceable by m

Re: [PHP-DEV] PHP 4.2.0 Release Announcement

2002-04-23 Thread Aaron Bannert
On Tue, Apr 23, 2002 at 06:20:18AM -0500, Rose, Billy wrote: > I have Apache 2.0.25 with PHP 4.2.0RC2 running in production now. Been > running since it was released. Can you please describe your architecture (platform, os rev, etc...) and tell us what configure parameters you gave to both apache

RE: [PHP-DEV] PHP 4.2.0 Release Announcement

2002-04-23 Thread Rose, Billy
Aaron Bannert [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, April 23, 2002 10:16 AM > To: Rose, Billy > Cc: PHP Developers Mailing List > Subject: Re: [PHP-DEV] PHP 4.2.0 Release Announcement > > > On Tue, Apr 23, 2002 at 06:20:18AM -0500, Rose, Billy wrote: > > I have Apache

Re: [PHP-DEV] PHP 4.2.0 Release Announcement

2002-04-23 Thread Brian Foddy
Aaron Bannert wrote: >>It didn't coredump for me on startup. >> > > Nor for I, and I've done quite a lot of testing on this thing. The > startup error has been identified (even though not reproduceable by me > for some reason) and I will supply a patch for that later today. There > is still anoth