Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:94062 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 90560 invoked from network); 16 Jun 2016 20:09:55 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Jun 2016 20:09:55 -0000 Authentication-Results: pb1.pair.com header.from=rowan.collins@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=rowan.collins@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.51 as permitted sender) X-PHP-List-Original-Sender: rowan.collins@gmail.com X-Host-Fingerprint: 74.125.82.51 mail-wm0-f51.google.com Received: from [74.125.82.51] ([74.125.82.51:34877] helo=mail-wm0-f51.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D2/1A-25388-29703675 for ; Thu, 16 Jun 2016 16:09:55 -0400 Received: by mail-wm0-f51.google.com with SMTP id v199so205610456wmv.0 for ; Thu, 16 Jun 2016 13:09:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:references:from:to:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=be9wwTRRt+VK28auND48qViQBFpTX755AzhDzFD7gHU=; b=T9LDzEP9nubtz5lBl64qeyL6ned7qvRPjHaZSYMbyc/WlNBGnEHVI7qo0vdtLVs6RN KskdoUbz1vhLebGiiTNaXHfEtC+nyiefdiZ/MYfnMDNhQ4MyZ1fbmWSDTeJ+Mn1nwEPj Ah5uyo+3fEKy7DqdWDS3X4K87dTKcIs9Vmv/9l+gXIl0BvVvjKnQVfxmKgk/BrOZEFkP /a+p9S0YWtPhIDhtS/16olalea6a0ji42mE1Qu1ZKzbippTtqHDm4R6Avn1TBWB6wyzp ZpwOSVgRYIzgDekzI2483Eit7R/iPDB61F8bmKSPZVpuJYxgmb++XdZwjaklIzC+p+c+ jbsw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:references:from:to:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=be9wwTRRt+VK28auND48qViQBFpTX755AzhDzFD7gHU=; b=ky2BFP0/KYfzg0U73JiL8RXWVE9ym6149ab2rbwMZrU3OeOBWSyB+AxDCG74n6Ktgn 8jRQOj3CW2OBQnrDEI2/4WjgSQ01Bfker3LWVADWAdeIHHTPgE+nW5+Q2B7/gxOXtaHC 85yiiuiIyqigQJH4WNIyVIZZRu2z7C5IEZHPPlc9vn746i8wN6qSQzPPcPyzpLt/dVZT I5cz6OjXVqlVpEBcVoPAzGkjLep7trWoOuVyOB5pZMDUc6emHKuvhphJQ4bNdwXg1ahH kK2vxsOx8+UYFzHI/7L4df+zkel1qK8Bqyv7vFI2EACD8U0GNR8ZvuIRBD/lVzoC+6XV XGFQ== X-Gm-Message-State: ALyK8tIFaNY73OfqYAEQ+kYwl2u5gZMyPcDHfUOkvIPP/SP2O5Wczfw6s42mmJQlZVMjxg== X-Received: by 10.28.0.130 with SMTP id 124mr17760471wma.23.1466107792119; Thu, 16 Jun 2016 13:09:52 -0700 (PDT) Received: from [192.168.1.5] ([2.25.96.65]) by smtp.googlemail.com with ESMTPSA id d137sm16427592wmd.12.2016.06.16.13.09.51 for (version=TLSv1/SSLv3 cipher=OTHER); Thu, 16 Jun 2016 13:09:51 -0700 (PDT) References: <6c03dafd-093a-0087-6312-96fede93c5f0@gmail.com> <1c437efe-7f1d-629f-cfbc-41cbcda38d89@fleshgrinder.com> To: PHP internals Message-ID: <0525d6ee-bb07-a716-4d21-b0e32be12ce9@gmail.com> Date: Thu, 16 Jun 2016 21:09:42 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; 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: 7bit Subject: Re: [PHP-DEV] Is the "No BC Breaks in Minor Releases" policy enforceable? From: rowan.collins@gmail.com (Rowan Collins) On 16/06/2016 19:11, Levi Morrison wrote: > On Thu, Jun 16, 2016 at 10:30 AM, Rowan Collins wrote: > >> > >> >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". > I didn't necessarily mean the currently proposed; I mean more > generally. For instance Nullable Types and the associated > ReflectionType changes both have small BC breaks that I don't mind. In > the case of the former there is a long-standing bug that did have BC > break impact that was fixed. Ah, fair enough, thanks for clarifying. As noted before, the nullable types case included careful analysis of small BC breaks that were a side-effect of a major new feature being released as part of 7.1. I wouldn't personally draw a distinction in between adding it in x.1 vs x.2 or x.3; either the BC hiccup is acceptable, or the feature should be roadmapped to x+1.0. But the ReflectionType case definitely feels like clean-up of 7.0, so makes sense to me as an example. Regards, -- Rowan Collins [IMSoP]