Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:94070 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 28969 invoked from network); 17 Jun 2016 09:24:34 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Jun 2016 09:24:34 -0000 Authentication-Results: pb1.pair.com smtp.mail=bjorn.x.larsson@telia.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=bjorn.x.larsson@telia.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain telia.com from 81.236.60.155 cause and error) X-PHP-List-Original-Sender: bjorn.x.larsson@telia.com X-Host-Fingerprint: 81.236.60.155 v-smtpout2.han.skanova.net Received: from [81.236.60.155] ([81.236.60.155:39266] helo=v-smtpout2.han.skanova.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FF/51-18862-1D1C3675 for ; Fri, 17 Jun 2016 05:24:34 -0400 Received: from [192.168.8.8] ([94.254.95.82]) by cmsmtp with SMTP id Dq0rbbbNQqtwZDq0rbJTgM; Fri, 17 Jun 2016 11:24:29 +0200 To: Rowan Collins , Levi Morrison References: <6c03dafd-093a-0087-6312-96fede93c5f0@gmail.com> <1c437efe-7f1d-629f-cfbc-41cbcda38d89@fleshgrinder.com> Cc: PHP internals Message-ID: <38f1b306-162f-1b10-1936-16d21f669152@telia.com> Date: Fri, 17 Jun 2016 11:24:30 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-CMAE-Envelope: MS4wfIlVsv2E7k7vzwMQM3TKhisIABzdVvxCi0/AreWFI/ONktAdExXGHXL0iE2JuOU4mp+b8SAJXolZcGHXzy3/CqBxDfuiiZT7v5+TtmRY6NoDHg4bX2mx BNLQS++L/YDMVA1CRbFcHpQckV+8Zkb80Gi91d+SPeLEodLMjQYqsWp8sxfa4ilolX3NXTH+ilyS+rRD0dMpGkKaE2O6Al7zd36slMPgzakie1Ek/LwHHrT+ eLVQU2tGOHJTmYxJX4nLDA== Subject: Re: [PHP-DEV] Is the "No BC Breaks in Minor Releases" policy enforceable? From: bjorn.x.larsson@telia.com (=?UTF-8?Q?Bj=c3=b6rn_Larsson?=) Den 2016-06-16 kl. 18:30, skrev Rowan Collins: > On 16/06/2016 17:24, Levi Morrison wrote: >>> I also have to say that to the very short timeline to finalize 7.0 >>> should not be paid by breaking BCs in 7.x. We can have a short >>> timeline for 8.0 as well. If we need more drastic BC breaks earlier >>> than expected. If JIT is a goal for 8.0, then let do the BC breaks in >>> 8.0 and prepare our users using 7.x. >> >> I agree with sentiment. However I do not mind certain BC breaks being >> made in 7.1. For 7.2 and beyond I think we should be significantly >> more strict on BC breakages. > > Why? What's special about 7.1? If it was a case of finishing off > changes that "should have been part of 7.0", I can see some kind of > logic, but the ones we're actually discussing seem to be more about > "preparing for 8.0". > > Regards, The statement above by Levi makes perfect sense in my eyes and what makes the early minor releases special after a major release is that the uptake of 7.x is not so large yet. So running a migration project from PHP 5.x targeting PHP 7 could go for either 7.0 or 7.1. Going for later minor releases finding minor BC breaks then requires another migration project, albeit small. Regards //Björn Larsson