Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:94003 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 25028 invoked from network); 15 Jun 2016 11:38:37 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Jun 2016 11:38:37 -0000 Authentication-Results: pb1.pair.com header.from=j.boggiano@seld.be; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=j.boggiano@seld.be; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain seld.be designates 74.125.82.54 as permitted sender) X-PHP-List-Original-Sender: j.boggiano@seld.be X-Host-Fingerprint: 74.125.82.54 mail-wm0-f54.google.com Received: from [74.125.82.54] ([74.125.82.54:36508] helo=mail-wm0-f54.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 14/2F-27860-B3E31675 for ; Wed, 15 Jun 2016 07:38:37 -0400 Received: by mail-wm0-f54.google.com with SMTP id f126so17780433wma.1 for ; Wed, 15 Jun 2016 04:38:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=seld-be.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=YX8usfVP7gikiIG4YARCmTg7soyHoyzi1Q46/fuBH30=; b=1DlpX6TCAp+VfXnMnj36tiie76xvXLpmr4OSJ/4u9EQD6xL0FIm1zJjozT3QiFe9RW vMnn3CxW/on5C1g+A0jQfP/JiSMa0WsPgP7yMLNB3jW/zmZzTz1Xyy807JIs1b8XdhLD /qxqeTYbIhVTQ8DAHgu0OUJXYtrt/0r/eyEia9y4wjZ4QP8ch+xpW4dJJV2P8QSGoFc5 E39fouBoJMzyz4QiPY6RgFkRBi7Xmxf1M5sQXDZ6JuWlJdtymAEZcRU1uWHN12e//tad zo6JaWslLWf+vPg5PUO7012FSAstuAhprkwp3sIAF8PQbQy+21jTBTqeZct/5TWJVfZs EZmg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=YX8usfVP7gikiIG4YARCmTg7soyHoyzi1Q46/fuBH30=; b=AUREqBsJZ/hS7QucHi3OVLTswORJciqdDmlXPxyOM0ZorPQIhTOIc+MfVes8wtVsGO h26prV8DdUFGz95/pwMR6csiMKcRGuJxwNi7Zret6+ADQREA1QAc4ZQcQbHbNvN1kIPC gjslDIUgcxmTtW6CYcFog1xOgkYWrwGkAA+HSuyXO+fM/w9sJ2RC39pag+T4Y6dVJil5 7yw175wgWKpJXaoRR489VHm7bSDM0JncNNGO4iRUyvYrL72hMFjOuNkfOmKkFe8CJ32+ +UmEeYVyJl8vtIInkNS+7BpNXtkOS0WwA7wYUarAasu0ePvfNwhsOxusdU/zRQhxVDmY Nhgw== X-Gm-Message-State: ALyK8tJ6FUEoWo6avkwivxbKp7BUHc4g3kH6GwA8gW4ZEtEmWQ/Ui44++sQOCr0p2H6DUA== X-Received: by 10.194.239.163 with SMTP id vt3mr10772467wjc.78.1465990713101; Wed, 15 Jun 2016 04:38:33 -0700 (PDT) Received: from [192.168.0.2] (cpc74585-lewi13-2-0-cust978.2-4.cable.virginm.net. [82.25.75.211]) by smtp.googlemail.com with ESMTPSA id n26sm7391701wmi.3.2016.06.15.04.38.30 for (version=TLSv1/SSLv3 cipher=OTHER); Wed, 15 Jun 2016 04:38:30 -0700 (PDT) To: internals@lists.php.net References: <6c03dafd-093a-0087-6312-96fede93c5f0@gmail.com> <1c437efe-7f1d-629f-cfbc-41cbcda38d89@fleshgrinder.com> Message-ID: <55d87b00-ebcd-6132-ea29-1978236930e7@seld.be> Date: Wed, 15 Jun 2016 12:38:35 +0100 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: 7bit Subject: Re: [PHP-DEV] Is the "No BC Breaks in Minor Releases" policy enforceable? From: j.boggiano@seld.be (Jordi Boggiano) On 15/06/2016 11:41, Pierre Joye wrote: > I also understand the needs to change, update, optimize or clean our > edge cases to open the path to JIT and the likes. However I would be > very careful about that, and Dmitry and the team are very careful. 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. +1 to that, it would be much better to introduce BC (strong/er) warnings in 7.1/7.2 and then if needed branch off 8.0 already so that JIT work can happen there with the BC warnings (and related features) removed. 8.0 could then come a year or two after 7.1 depending on how the JIT work progresses. This would keep the "BC promise" intact instead of going back to cowboy php days. We are finally seeing more rapid PHP version adoption and I think it would be a shame to break the trust PHP gained in the last few years of stable and predictable releases. Cheers -- Jordi Boggiano @seldaek - http://seld.be