Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:94046 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 57281 invoked from network); 16 Jun 2016 16:24:11 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Jun 2016 16:24:11 -0000 Authentication-Results: pb1.pair.com header.from=morrison.levi@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=morrison.levi@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.174 as permitted sender) X-PHP-List-Original-Sender: morrison.levi@gmail.com X-Host-Fingerprint: 209.85.192.174 mail-pf0-f174.google.com Received: from [209.85.192.174] ([209.85.192.174:34075] helo=mail-pf0-f174.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 1A/E3-25388-AA2D2675 for ; Thu, 16 Jun 2016 12:24:11 -0400 Received: by mail-pf0-f174.google.com with SMTP id h14so6251462pfe.1 for ; Thu, 16 Jun 2016 09:24:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=537N3cc3OxRsQQTlwQx1P5+UacZ0+LnYCY/lybiHifY=; b=RPqcRcqbGX6yTwftqizNs5on33MeXmO7y74fGcEgXil5Qr9i0EIS4/NQcq4vkNiRGq 2ztno5aZd6cjchcsFRcc1IjB6cygh36ab8GgYAHh9Co7gOFRftSwOaHOSpVNG/YtV8Mw gdtt2sxymoTpTUJWqXq2nWBAYp9/mE5nhGJDTIPtm9l8UHz5LLjxgHU5xKlEJg3XS4Sg 0EYYsopiTZyM/VnQI6jTaRIFfmdRWd40fHWG3yJZNis/GGNQq25VF8yMr9JKJDLRjacU gIDWoZYvYawt7y45PXE61hYNaRci5Dayi/rRpTI1VndNIL+AHL1KFEvHqkHxH1arvGwp q7YQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=537N3cc3OxRsQQTlwQx1P5+UacZ0+LnYCY/lybiHifY=; b=Hn+rv01fekTN81nG3E0atwPQErfX06QhEnRpe1FI68vKL/sZH4nRi6PTHvCaL0cwE7 XIwomdKWcghvObjW9R45pad3jMAOt5EK8uAgRWh5JmUCVqZGMtHBK8+NBTSdgEAFYLht ZxNY4R0yD1H8QM3awu4bbFQ6RYUjBVayRXpUjYZcGOBOGdZmO2QhffF8G8JVfhjarK+w IahXqJOLxFHm3TAGAcB8VoaiLs0iJQxRr+6+oQDtMnpMK+lH8DFdmcruQ4yw7QcDTbsX un+QbAhm1t7s0MO37mmz75ifxmJZ7M8/Y4vJeg7Zy01Z5YktgctoqWNeuJfVfyuqyOD6 G0Iw== X-Gm-Message-State: ALyK8tLCjCU/LcSKOuGYE2a+DGfq4ANywXMXvunwfMtrQ/Q9JCcabq7eW5a7wb4qn4qp8p1FbT2xjl2sJGN0eA== X-Received: by 10.98.65.209 with SMTP id g78mr6148637pfd.93.1466094248114; Thu, 16 Jun 2016 09:24:08 -0700 (PDT) MIME-Version: 1.0 Sender: morrison.levi@gmail.com Received: by 10.66.236.137 with HTTP; Thu, 16 Jun 2016 09:24:07 -0700 (PDT) In-Reply-To: References: <6c03dafd-093a-0087-6312-96fede93c5f0@gmail.com> <1c437efe-7f1d-629f-cfbc-41cbcda38d89@fleshgrinder.com> Date: Thu, 16 Jun 2016 10:24:07 -0600 X-Google-Sender-Auth: FEwkDOir8ryzAr1lAtuLS8AneKw Message-ID: To: Pierre Joye Cc: PHP internals , Dmitry Stogov , Rowan Collins Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] Is the "No BC Breaks in Minor Releases" policy enforceable? From: levim@php.net (Levi Morrison) > 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.