Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:8869
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Thu, 1 Apr 2004 09:25:21 -0800 (PST)
To: Ilia Alshanetsky <ilia@prohost.org>
cc: internals@lists.php.net
In-Reply-To: <200404011209.31299.ilia@prohost.org>
Message-ID: <Pine.LNX.4.58.0404010924080.1348@thinkpad.lerdorf.com>
References: <5.1.0.14.2.20040401143302.021ae848@127.0.0.1>
 <200404010919.13175.ilia@prohost.org> <Pine.LNX.4.58.0404010901520.1348@thinkpad.lerdorf.com>
 <200404011209.31299.ilia@prohost.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Re: [PHP-DEV] Releasing 4.3.5pl1
From: rasmus@php.net (Rasmus Lerdorf)

On Thu, 1 Apr 2004, Ilia Alshanetsky wrote:
> On April 1, 2004 12:05 pm, you wrote:
> > Yup, given the fact that the DST change date is fast approaching, it would
> > be good to get the mktime/gmmktime fixes out there soon along with the
> > strftime fix.  Nothing says we have to wait until we have 100+ bug fixes
> > in there.  We have fixed 20 or so bugs since 4.3.5 and I see nothing wrong
> > with pushing out a 4.3.6 with these 20 fixes now.
> 
> While, some fixes are fairly safe, others may raise issues we had not 
> considered (ex. fix for bug #27782). if we are making a quick release without 
> a prior testing (RC) process I'd prefer to have only the absolutely necessary 
> fixes such as DST & TSRM.

I don't think we should push it out without an RC.  I just think we should 
instigate the RC process now rather than waiting.  Especially considering 
the fact that there were some non-trivial changes.  The more other changes 
we add on top of these, the more time we will need for RC.

-Rasmus