Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:79082 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 17442 invoked from network); 21 Nov 2014 15:16:51 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Nov 2014 15:16:51 -0000 Authentication-Results: pb1.pair.com header.from=zeev@zend.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=zeev@zend.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 74.125.82.49 as permitted sender) X-PHP-List-Original-Sender: zeev@zend.com X-Host-Fingerprint: 74.125.82.49 mail-wg0-f49.google.com Received: from [74.125.82.49] ([74.125.82.49:50481] helo=mail-wg0-f49.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 54/E2-32393-1675F645 for ; Fri, 21 Nov 2014 10:16:50 -0500 Received: by mail-wg0-f49.google.com with SMTP id x12so6810841wgg.8 for ; Fri, 21 Nov 2014 07:16:46 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=n05delBMr8FZL/Ym2IjGlv9UcVMPjnwAhp6w7ScF6zc=; b=RBSYqSevu0UeO7c7NUgTmOde7p/DALrlM231gRY4BDVzcse6pq4om1W5q6znvyGNk3 y/FdQYytwBXyiNdlznZkJWeA1Rde8t/bhMrWgSNbRcRMoxMheskhYAwONSBR99S4QRz9 qjf2ZlY4Gio2pZZVpaRrrrWfSmcqlQzf1DBOy5iRiL2QrMMxJZtO/hojrKQNkJqCdMPD DRt9ZfISwlXqTVzELyQ024UZavlb9M9d9PU+/DYP32rLQcC3Xqevowcxec6eV9LUeRL4 Ir98ayUpgoBpNgUASaOWt3KekQKfRvE25HNs8fTK591YLdixOnEtyZkfhXjiN2g3hYrw Ojjw== X-Gm-Message-State: ALoCoQlhIug9xf+Jflgmxmc/qhOmJ9qVxcno7+Q6YTmigDXZ/WkqA9YPIKiYoRoQt5DCDe7dF/1c9gH5wRyXeUgLLgRk1Im8uzD43dUVRpyBPV9FXE+jzmc6Pb7zM8l2eIBeZL6Pw+rfhN/iN/TSLgCR/akmOuCiJQ== X-Received: by 10.194.250.105 with SMTP id zb9mr8335894wjc.123.1416582632626; Fri, 21 Nov 2014 07:10:32 -0800 (PST) Received: from [10.160.191.159] ([2.54.6.89]) by mx.google.com with ESMTPSA id v6sm8398280wjz.40.2014.11.21.07.10.31 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 21 Nov 2014 07:10:32 -0800 (PST) Content-Type: multipart/alternative; boundary=Apple-Mail-6FC3F92A-C6CA-4D2B-98B8-85962AB9F0E6 Mime-Version: 1.0 (1.0) X-Mailer: iPhone Mail (12B436) In-Reply-To: Date: Fri, 21 Nov 2014 17:10:30 +0200 Cc: Joe Watkins , PHP internals Content-Transfer-Encoding: 7bit Message-ID: References: <3d131946349b68aa2ae26dcfeaa5197a@mail.gmail.com> <1416557888.27517.21.camel@localhost.localdomain> To: Kris Craig Subject: Re: [PHP-DEV] [VOTE] [RFC] PHP 7.0 timeline From: zeev@zend.com (Zeev Suraski) --Apple-Mail-6FC3F92A-C6CA-4D2B-98B8-85962AB9F0E6 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Kris, This existed in the RFC since the get go and I don't believe anybody raised a= ny concerns about it. There was plenty of time for discussion. Either way a= pproval of this RFC won't have any effect on the approval or rejection of ot= her RFCs. Kris, All - I'm now on a 7th day straight of a paralyzing 39.5C temperature.= Let's focus on what matters. I at least don't have energy to respond to t= he rest. Zeev > On 21 =D7=91=D7=A0=D7=95=D7=91=D7=B3 2014, at 12:16, Kris Craig wrote: >=20 > Specifically, this is the sentence that just seems completely out of place= : >=20 > "Arguably, while we should definitely take the opportunity to implement co= mpatibility-breaking changes in 7.0, we also shouldn't turn it into a compat= ibility-breaking festival, as the more we break, the more likely it is users= would delay upgrades, stay with old, insecure versions - or even consider o= ther alternative options." >=20 > Mind you, I don't necessarily disagree with this opinion, but I don't thin= k it belongs in this RFC as people's votes to approve the timeline could lat= er be construed as endorsements of the BC philosophy you expressed, as well.= That bothers me, probably enough to make me vote against this, so I really= hope you remove it. I'd certainly have no objection to seeing that expande= d into its own RFC, though. =3D) >=20 > --Kris >=20 >=20 >> On Fri, Nov 21, 2014 at 2:12 AM, Kris Craig wrote:= >>=20 >>=20 >>> On Fri, Nov 21, 2014 at 12:18 AM, Joe Watkins wr= ote: >>> On Fri, 2014-11-21 at 10:07 +0200, Zeev Suraski wrote: >>> > After some Twitter hints that I should get my act together and finally= move >>> > this to a vote, it=E2=80=99s finally happening: >>> > >>> > >>> > >>> > https://wiki.php.net/rfc/php7timeline#vote >>> > >>> > >>> > >>> > Cast your vote! >>> > >>> > >>> > >>> > Zeev >>>=20 >>> Morning Zeev, >>>=20 >>> Proposed milestones column needs to change from mid October to >>> November. >>>=20 >>> Cheers >>> Joe >>>=20 >>>=20 >>> -- >>> PHP Internals - PHP Runtime Development Mailing List >>> To unsubscribe, visit: http://www.php.net/unsub.php >>=20 >> Looks good, except I think you should remove the language expressing opin= ion about the general merits of backwards compatibility, as that falls outsi= de the scope of the timeline being voted on. Plus it's an issue that really= should be discussed and, if needed, voted on separately, not as a single se= ntence stuffed into an RFC about a release timeline. If I were to vote yes o= n this timeline, I would not want my vote interpreted as an endorsement of t= hat position on BC. I think it's overreach and scope creep that should be r= emoved. >>=20 >> Other than that one serious (but easily fixable) flaw, I think it's great= ! >>=20 >> --Kris >=20 --Apple-Mail-6FC3F92A-C6CA-4D2B-98B8-85962AB9F0E6--