Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:50558 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 23334 invoked from network); 25 Nov 2010 17:49:25 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Nov 2010 17:49:25 -0000 Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.42 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.161.42 mail-fx0-f42.google.com Received: from [209.85.161.42] ([209.85.161.42:57240] helo=mail-fx0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 31/18-16484-4A1AEEC4 for ; Thu, 25 Nov 2010 12:49:25 -0500 Received: by fxm11 with SMTP id 11so987023fxm.29 for ; Thu, 25 Nov 2010 09:49:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=4L6jJLIGKH2gTKLLjJ17UIba7pzJSCb/qSjf2QV3q24=; b=axJ5V3b7YKcaC4+NjGkrGfrtFucEoIJP7skX1GWHY8scViIrCWi98T5KBSuO12u+zM MJBN/cKqpjJGIzUB8IZPZvD/rH+eZoVNHAECXo6FPbaPHFRJ1EYUigXnfPDEzkYc/47Y d+9xPn96AIYE6JS8jqeF6lOqJWro0E7Vb+VH8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=mlOcLWCxhBXfbT7l/vh3Fy3zltXcjYytvuYXFw1/N80j4LyJPvk8STYaxATNXz4akP Vozf8UShGZVKDAbvDav4cFczOc8+MuQPuX/IWKVD01pWVzaQ6/bwGTR4KVGDsLcslnRE EXEmZL9ebdaOX79rgea2cpHUyZ7O8u0hP8GIY= MIME-Version: 1.0 Received: by 10.223.125.136 with SMTP id y8mr1034272far.149.1290707360311; Thu, 25 Nov 2010 09:49:20 -0800 (PST) Received: by 10.223.83.142 with HTTP; Thu, 25 Nov 2010 09:49:20 -0800 (PST) In-Reply-To: <8757232E56758B42B2EE4F9D2CA019C9154C7D@US-EX2.zend.net> References: <73.C4.59959.876BBEC4@pb1.pair.com> <3EA67EA2-A9B1-4DFB-8A30-05B37BCA313B@iki.fi> <8757232E56758B42B2EE4F9D2CA019C9154B70@US-EX2.zend.net> <1290705653.7033.73.camel@guybrush> <4CEE9C5F.3040206@lerdorf.com> <8757232E56758B42B2EE4F9D2CA019C9154C7D@US-EX2.zend.net> Date: Thu, 25 Nov 2010 18:49:20 +0100 Message-ID: To: Andi Gutmans Cc: Rasmus Lerdorf , =?ISO-8859-1?Q?Johannes_Schl=FCter?= , Jani Taskinen , "davey@php.net" , PHP Internals Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] Re: Hold off 5.4 From: pierre.php@gmail.com (Pierre Joye) 2010/11/25 Andi Gutmans : >> -----Original Message----- >> From: Rasmus Lerdorf [mailto:rasmus@lerdorf.com] >> Sent: Thursday, November 25, 2010 9:27 AM >> To: Johannes Schl=FCter >> Cc: Andi Gutmans; Jani Taskinen; davey@php.net; PHP Internals >> Subject: Re: [PHP-DEV] Re: Hold off 5.4 >> >> Looking through trunk I think we are in pretty good shape. =A0I don't th= ink cherry- >> picking and branch merging is an issue at this point. =A0A >> 5.4 with the performance improvements, Traits, minus the type hinting >> breakage is something we can get out pretty quickly without causing any = sort of >> PHP 6 confusion or breaking existing apps. > > > Btw, just to be clear I am also OK with this approach. I just wanted to m= ake sure we consider the pros/cons of doing minor vs. major so we're all al= igned re: the implications :) =A0I would pass on any type hinting patch bec= ause there's no consensus and if we rip it out we are pretty much set to go= (and I do not see a major negative implication of taking it out). Less is = more IMO and it will enable us to get good functionality out sooner. We wil= l probably make some more engine enhancements during pre-beta but can freez= e at any point in time. Agreed here as well. I think we can begin with the release in January (I mean actually begin with the 1st test release). That lets us a couple of weeks (don't forget December has some family mandatory activities for most of us :) to actually get the RFC sorted out and review what we have. By review I mean to actually focus on evaluating trunk from a BC/QA/design point of view. I'm not saying it is badly designed or whatever else negative, but that most of us were busy with the current active branches and other bugs. I'm sure these 2-3 weeks more will benefit the php-next release and will make us feel much more confident about it, from day 1. Cheers, -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org