Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:79724 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 25786 invoked from network); 16 Dec 2014 15:23:21 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Dec 2014 15:23:21 -0000 Authentication-Results: pb1.pair.com smtp.mail=zeev@zend.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=zeev@zend.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.212.179 as permitted sender) X-PHP-List-Original-Sender: zeev@zend.com X-Host-Fingerprint: 209.85.212.179 mail-wi0-f179.google.com Received: from [209.85.212.179] ([209.85.212.179:38736] helo=mail-wi0-f179.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 5D/81-12185-76E40945 for ; Tue, 16 Dec 2014 10:23:21 -0500 Received: by mail-wi0-f179.google.com with SMTP id ex7so12893376wid.6 for ; Tue, 16 Dec 2014 07:23:16 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=a5XDBCpNnJXQT88amqboCFn+P8eJi2r4cBQhegVORms=; b=iy0wqZesqDAUsK9XTj/BkCwXTCdlmpjez1LuNS9AIOFSLzGG0OMfSAFK6jHAnD9xfl Mc2U2pKTq2YOB7TeMvUiOrk97M5HW93EcTyutHVXayM6VTrx5kcThDf48IacoJS0mOTy zmNTd+d62q/5wRwvkCCE4grUGWKB/g+MM2LxE2K502qESNudnjI+9jz0I1IkGiMa8wPR DOcEGbZ3X8OzIUY3GdPdyueGG3nCCn2wGk4SooEAUc9Z+NrqXZ0Yq7Frzh21qMARbhpk moX5vEfdcayKCGSvRutyfz7U+o8FdA8bkQQLveUOJRjDPn4viVg2vUn+70JNhMOwc6r7 iVpg== X-Gm-Message-State: ALoCoQl4TT0PJIj3TPa3MISsr/hbl5fXh/CyIKvSr/6auRb/4TCnU9AT6PPHyGQAv8EhCAsJ9aJFAAMJyLHo8ARMby6YIGslGY2T0HDyHqqUrsRidTFLzXDjh/TjhM1hvbc/7+j3DeCybFBjhqrclRud2qwUcea93Q== X-Received: by 10.181.28.165 with SMTP id jp5mr5796057wid.76.1418743396704; Tue, 16 Dec 2014 07:23:16 -0800 (PST) References: <8C1EFD82-CFE0-4D01-9231-2A1658B182A6@ajf.me> In-Reply-To: MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQHEAwp930Oucd9RrwDs9oQRz4U5JAKjqEmtAMffvUycjyTywA== Date: Tue, 16 Dec 2014 17:23:10 +0200 Message-ID: To: Levi Morrison , Xinchen Hui , Andrea Faulds Cc: PHP Internals Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: RE: [PHP-DEV] [RFC] PHP 5.7 From: zeev@zend.com (Zeev Suraski) > -----Original Message----- > From: morrison.levi@gmail.com [mailto:morrison.levi@gmail.com] On > Behalf Of Levi Morrison > Sent: Tuesday, December 16, 2014 9:29 AM > To: Xinchen Hui > Cc: Andrea Faulds; PHP Internals > Subject: Re: [PHP-DEV] [RFC] PHP 5.7 > > >> There has been some debate about whether to make =E2=80=9CPHP 5.7". I = have > made a very simple RFC. It proposes a final minor version of PHP 5, PHP > 5.7, > to be released at the same time as PHP 7, with no new features whatsoever= . > >> > > I am wondering why we need that? no new features.... > > > > I think we can extend 5.6 release cycle to avoid that.. > > Extending the PHP 5.6 release cycle doesn't give an opportunity to raise > different E_STRICT and E_DEPRECATED messages in preparation for PHP 7.0. > This may or may not be something you value, but it's something I > personally > value. I don't see why we'd need new E_STRICT's, but what stops us from adding E_DEPRECATED to 5.6.x? I think the likelihood of getting these notices in the hands of people goes way higher if we put it into 5.6.x, which will be perceived as a bug-fix release, than a 5.7.0, which will be perceived as a feature release. Zeev