Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:8866 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 79992 invoked by uid 1010); 1 Apr 2004 17:05:27 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 79784 invoked from network); 1 Apr 2004 17:05:26 -0000 Received: from unknown (HELO colo.lerdorf.com) (66.198.51.121) by pb1.pair.com with SMTP; 1 Apr 2004 17:05:26 -0000 Received: from rasmus2.corp.yahoo.com (rasmus2.corp.yahoo.com [207.126.233.18]) by colo.lerdorf.com (8.12.11/8.12.11/Debian-3) with ESMTP id i31H5FqK005486; Thu, 1 Apr 2004 09:05:15 -0800 Date: Thu, 1 Apr 2004 09:05:10 -0800 (PST) X-X-Sender: rasmus@thinkpad.lerdorf.com To: Ilia Alshanetsky cc: internals@lists.php.net In-Reply-To: <200404010919.13175.ilia@prohost.org> Message-ID: References: <5.1.0.14.2.20040401143302.021ae848@127.0.0.1> <200404011451.10763.edink@emini.dk> <200404010919.13175.ilia@prohost.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Status: No, hits=-4.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on colo 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 07:51 am, Edin Kadribasic wrote: > > +1 except I would call it 4.3.6. We have precedent for this sort bug fix > > release. 4.3.1 if I remember correctly. > > +1 > > > There were many bug reports regarding some data/time functions, maybe we > > should merge that fix in as well? Rasmus/Derick should know more about this > > one,. > > If we decide to make 4.3.6 I think we should include this fix as well, as it > affects a fairly large number of users as well. 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. -Rasmus