Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:78105 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 68333 invoked from network); 16 Oct 2014 00:28:39 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Oct 2014 00:28:39 -0000 Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass 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.213.47 as permitted sender) X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.213.47 mail-yh0-f47.google.com Received: from [209.85.213.47] ([209.85.213.47:45570] helo=mail-yh0-f47.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B1/52-55527-6311F345 for ; Wed, 15 Oct 2014 20:28:38 -0400 Received: by mail-yh0-f47.google.com with SMTP id c41so1124529yho.34 for ; Wed, 15 Oct 2014 17:28:36 -0700 (PDT) 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=3LC+DXzh30GBDTJ+ehGJVWr/yg7CcLxWus4eA3vSyEA=; b=CzRYH5vX74VfIa64PjpRPxKoCmW10GJd9VTBaw6OPALqoes53ebCrmkM5OYKDkP7+n MuKcYvfa+LIxDs53ST0R1vb4YC0Dp/owFwX2etFCv6FHA2xBxS/Jf3zRHIIIJX0SwCPt BXL0RHFG9vYQHaRiS47cKwT0/wGp5oXCg9X0HIfmOy+IGcQJUbfi9BU8p18R/ztyyXvy /q3ovwt/AB6+1TJNSrU+D0JYSxqvd71FGx9mnEjA/wBYE0BX7jV3ZnHwm0aLPjuLxm0t VpAz5bLMMyJAy2zZ6OCdsOnBIIG1vrsV3dkdutNyIifvw4bpaQkBRRDqFMTPk8os39Sg 4LxQ== MIME-Version: 1.0 X-Received: by 10.236.45.74 with SMTP id o50mr22287857yhb.68.1413419315975; Wed, 15 Oct 2014 17:28:35 -0700 (PDT) Received: by 10.170.68.134 with HTTP; Wed, 15 Oct 2014 17:28:35 -0700 (PDT) In-Reply-To: <32b8315ede38cd03ad4a7ab4497397e9@mail.gmail.com> References: <32b8315ede38cd03ad4a7ab4497397e9@mail.gmail.com> Date: Thu, 16 Oct 2014 02:28:35 +0200 Message-ID: To: Zeev Suraski Cc: PHP internals Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] RFC: PHP 7.0 timeline From: pierre.php@gmail.com (Pierre Joye) hi Zeev, On Tue, Oct 14, 2014 at 10:08 AM, Zeev Suraski wrote: > All, > > > > We=E2=80=99ve had some discussions about it during the version name & php= ng RFC > processes, and now that 5.6.0 is behind us =E2=80=93 I think it=E2=80=99s= time to get a > more concrete game plan for PHP 7.0. > > > > I drafted an RFC that proposes a one year timeline for PHP 7.0. I believ= e > it strikes a good balance between early delivery to stay competitive, and > having enough time to shape a major version. Given that we=E2=80=99ve al= ready made > some very substantial progress towards 7.0 (with phpng, AST, uniform > variable syntax, etc.) =E2=80=93 I think that timeline is very realistic,= and > perhaps we can even beat it. Restating the obvious, new features that > don=E2=80=99t have compatibility implications can always be delivered in = minor > versions, i.e. 7.1, 7.2, etc. > > > > The RFC is at https://wiki.php.net/rfc/php7timeline - comments welcome! So I have to say (again) that one year is too short. We discussed 1.5 year as a good realistic timeline and that's what I am going to propose using a competitve RFC today, unless you are willing to add the options to this RFC (would be easier). The need of a 5.7 release is also something we need to decide. I am not saying we cannot make it in less than 1.5 year, but one year, given the current status, is not realistic. Given that the engine is still a moving target, it is not realistic, fair nor correct to ask other developers to get their stuff done by 2015/1 or 2015/2, it is simply not the way I see cooperation and support for other php.net developers. Cheers, --=20 Pierre @pierrejoye | http://www.libgd.org