Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:78049 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 63086 invoked from network); 14 Oct 2014 18:33:02 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Oct 2014 18:33:02 -0000 Authentication-Results: pb1.pair.com header.from=jonwage@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=jonwage@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.44 as permitted sender) X-PHP-List-Original-Sender: jonwage@gmail.com X-Host-Fingerprint: 209.85.215.44 mail-la0-f44.google.com Received: from [209.85.215.44] ([209.85.215.44:42349] helo=mail-la0-f44.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 21/B0-18603-C5C6D345 for ; Tue, 14 Oct 2014 14:33:01 -0400 Received: by mail-la0-f44.google.com with SMTP id hs14so9090341lab.17 for ; Tue, 14 Oct 2014 11:32:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=0M0XCQo9vf5kgkcXyBcY5/eLBTe23eXNFIlh/aPvTf8=; b=ilXkCt8Jr+fQZLImWBFv6e6/IgonrP8xkzr6ekADKhBvHzI/cYTeM3fZRVU1jAJvuk uOWiVElnp/pKJHulDf581zP3zUkuf9skDIkWvu3C4l1g6xNv40PsdkEs2eAZTSwLZ7Nb dkD2PMF/vAUlLEcmSLRr3KcdVcVePlR/J6hFDwxIqHepRcFC5P/X45bJU3ZtUqWVgv8s 5+wmFSMX28K1dD/AYkIfAKb9Yp/ozfttNYiT6wBav7gKxTYUupfJZWDNd6IhbEnrl2s6 4B2Ch+lN3L36SYXjLllWcWiD1bo7kJjINQA2rTzASSitQxJZGI01VEZPK8Bry6KwHvFP WCHg== X-Received: by 10.152.20.98 with SMTP id m2mr7297323lae.59.1413311578080; Tue, 14 Oct 2014 11:32:58 -0700 (PDT) MIME-Version: 1.0 Received: by 10.112.9.37 with HTTP; Tue, 14 Oct 2014 11:32:37 -0700 (PDT) In-Reply-To: <32b8315ede38cd03ad4a7ab4497397e9@mail.gmail.com> References: <32b8315ede38cd03ad4a7ab4497397e9@mail.gmail.com> Date: Tue, 14 Oct 2014 13:32:37 -0500 Message-ID: To: Zeev Suraski Cc: PHP internals Content-Type: multipart/alternative; boundary=089e01419b5c918e4b0505663edc Subject: Re: [PHP-DEV] RFC: PHP 7.0 timeline From: jonwage@gmail.com (Jonathan Wage) --089e01419b5c918e4b0505663edc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I like the 1 year timeline. It is an aggressive but achievable goal. On Tue, Oct 14, 2014 at 3: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! > > > > Zeev > --=20 Connect with me on *http://twitter.com/jwage* --089e01419b5c918e4b0505663edc--