Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:44317
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 63.205.162.117 as permitted sender)
Message-ID: <4A37EA3F.3010704@zend.com>
Date: Tue, 16 Jun 2009 11:53:51 -0700
Organization: Zend Technologies
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: Lukas Kahwe Smith <mls@pooteeweet.org>
CC: Derick Rethans <derick@php.net>, 
 'PHP Internals' <internals@lists.php.net>
References: <4A31462B.1070302@zend.com> <alpine.DEB.2.00.0906161005210.5761@kossu.ez.no> <E313C99E-EB76-490F-917D-C4D1A8648AB5@pooteeweet.org> <4A37CEC2.7050001@zend.com> <0FD8F38A-205D-4B79-AE8A-E7AFE475BC17@pooteeweet.org>
In-Reply-To: <0FD8F38A-205D-4B79-AE8A-E7AFE475BC17@pooteeweet.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: bug #48247 again
From: stas@zend.com (Stanislav Malyshev)

Hi!

> so if this issue is also in 5.2 .. i feel even less inclined to delay a 
> stable 5.3 release because of this issue. have we made it worse in our 
> attempts to fix it? the fact that this bug isnt fixed yet could mean 

No, it was crash before, now it doesn't crash for me but produces 400K 
of errors. One can argue it's better now, though pretty marginally as in 
both cases system can not be considered stable. Of course, there's an 
easy workaround of setting the timezone.

> 1) the issue affects few users
> 2) the issue is so complex that we continuously try to fix it and fail

We didn't "continuously" try to fix it - we applied one fix for the 
crash (which was caused by different reason than the loop), and need 
another for the loop.
As for why people don't complain more - I guess it's because it has 
obvious workaround and once people don't have it anymore many are too 
lazy to complain about the problem which now is not their problem :)

> both issues do not sound like good reason to delay 5.3 from where i stand.

We don't need to delay it if we decide to commit my (incomplete) fix 
now. Anyway, it's your decision, one of the three: 1. leave it as is, 2. 
commit incomplete fix now, 3. wait for complete fix. I agree 3 is the 
worst, I'd go with 2 but if you decide to go with 1 that's OK.
-- 
Stanislav Malyshev, Zend Software Architect
stas@zend.com   http://www.zend.com/
(408)253-8829   MSN: stas@zend.com