Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:58515 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 66976 invoked from network); 2 Mar 2012 19:05:47 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 2 Mar 2012 19:05:47 -0000 Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.170 as permitted sender) X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.214.170 mail-tul01m020-f170.google.com Received: from [209.85.214.170] ([209.85.214.170:37793] helo=mail-tul01m020-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 6A/29-22821-A0A115F4 for ; Fri, 02 Mar 2012 14:05:46 -0500 Received: by obbwd1 with SMTP id wd1so2531173obb.29 for ; Fri, 02 Mar 2012 11:05:44 -0800 (PST) Received-SPF: pass (google.com: domain of pierre.php@gmail.com designates 10.60.3.9 as permitted sender) client-ip=10.60.3.9; Authentication-Results: mr.google.com; spf=pass (google.com: domain of pierre.php@gmail.com designates 10.60.3.9 as permitted sender) smtp.mail=pierre.php@gmail.com; dkim=pass header.i=pierre.php@gmail.com Received: from mr.google.com ([10.60.3.9]) by 10.60.3.9 with SMTP id 9mr4073397oey.49.1330715144385 (num_hops = 1); Fri, 02 Mar 2012 11:05:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=pqFBLzc8J3I7F6Sz7Xn14DC/q3xn0ODEMJ9wk6fORdQ=; b=wz//MMtG6v8dBhKUBP0RnlOlTOwdxIdruCvSVcdGrFUFxTMpDjQsY64tDI0S56tKYh NJ8YNBEHxoauKyj7m50aroKsZpVdBMPc+B0bBmJ7JUmKKUq6jD9W7GUKs1w1tGZmLMYU 1aOZWYEMr2GoW2iXzymFlpuO9OO0Ok8EhStDIuPx8zZ5Xfo4Br4Uq6RQ1ilMBwpM31Lj jRG3aF/cRwhT1SIGD41j2skAXsviKu4wLrD9nt7mCQf3gz/sG70edyszZZWtttE+ox2b 6unhN60iWuG2MNljOgr+ZRUgML8tHJC6RnSdFhUzXBfxIHmt5hJaf+1R3O9hvm7YjCiY L4NQ== MIME-Version: 1.0 Received: by 10.60.3.9 with SMTP id 9mr3537721oey.49.1330715144330; Fri, 02 Mar 2012 11:05:44 -0800 (PST) Received: by 10.182.39.198 with HTTP; Fri, 2 Mar 2012 11:05:44 -0800 (PST) In-Reply-To: References: Date: Fri, 2 Mar 2012 20:05:44 +0100 Message-ID: To: Kris Craig Cc: Ferenc Kovacs , David Soria Parra , internals@lists.php.net Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] HEADS UP: 5.4 branch is open again From: pierre.php@gmail.com (Pierre Joye) that's totally off topic... but we have no idea yet when will be php 6, or whatsoever. However next is in around a year :) On Fri, Mar 2, 2012 at 8:00 PM, Kris Craig wrote: > From the timelines I've seen floating around, I was under the impression > that the next one would be 5.5, followed by 5.6, etc. =A0PHP 6 is at leas= t a > few years off according to every projection I've seen. > > --Kris > > > On Fri, Mar 2, 2012 at 1:26 AM, Ferenc Kovacs wrote: > >> On Fri, Mar 2, 2012 at 1:33 AM, David Soria Parra wrote: >> >> > Hi internals, >> > >> > just a heads up. The PHP_5_4 branch is open for commits again. >> > >> > - David >> > >> > -- >> > PHP Internals - PHP Runtime Development Mailing List >> > To unsubscribe, visit: http://www.php.net/unsub.php >> > >> > >> On a somehow related topic: >> Now that we have 5.4 out, I have a question: >> Do we know what will be the next major release? >> If we want to follow the releaseprocess RFC, I think it would be nice to >> think about whether we plan to roll out a major or a minor version next. >> By the RFC, we can't do such changes to the language as we did with >> 5.2->5.3 or 5.3->5.4, because userland BC breaks aren't allowed. >> So I can see two way to address this: >> If we can agree upon the next version number beforehand, and we decide t= hat >> we will go with the major release (be that php 6 or 7, whatever), we don= 't >> to do anything right now, we can branch the version from trunk/master, w= hen >> the time comes. >> If we can't agree upon the next version number, or we agree upon that th= ere >> will be an 5.5 version, I think it would make sense to create a branch f= or >> it ASAP, so there is place (trunk/master) for the approved but backward >> incompatible changes, and people don't have to hold patches. >> What do you think? >> >> -- >> Ferenc Kov=E1cs >> @Tyr43l - http://tyrael.hu >> --=20 Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org