Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:77965 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 19772 invoked from network); 14 Oct 2014 10:06:10 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Oct 2014 10:06:10 -0000 Authentication-Results: pb1.pair.com header.from=phoenix@jonstirling.co.uk; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=phoenix@jonstirling.co.uk; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain jonstirling.co.uk from 209.85.212.172 cause and error) X-PHP-List-Original-Sender: phoenix@jonstirling.co.uk X-Host-Fingerprint: 209.85.212.172 mail-wi0-f172.google.com Received: from [209.85.212.172] ([209.85.212.172:63926] helo=mail-wi0-f172.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 18/27-15889-195FC345 for ; Tue, 14 Oct 2014 06:06:10 -0400 Received: by mail-wi0-f172.google.com with SMTP id n3so9611933wiv.11 for ; Tue, 14 Oct 2014 03:06:06 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=bB7xfzjsmKYDtn8B6z6VB9OGDpEdrfPjM92lXdm6zMc=; b=X4iboOAgh3Qxq1sVpos/pFd901RfJ0wx5Luzm84byNyzgVxo2LwRNW6MQ+lXclykUS mMx+jqeEsRQvTcQnrDj1tUkzace4XozA0OzQqzoAyR+gnb+1Cqou1POII0p5ji51eci6 iTGiwgSp0dVvLHcj+G1XSUTkuLjA7M6dDXCznSh6/pmSQ3e2TmfhU/Kbt0SS1gB+SmIZ W+PvcydjDCPyolRkhx1mX97VKAJB+EilPYdJsSnyyMurd8emHlMZUAKlc2tMaDcOg2d8 sS1RzZnq94VKHN9/3IBNDBt1ovYJN9hBxHUrQ/fiaPP3At70/FPdhx7C4Kg/fz+isv1R EaUA== X-Gm-Message-State: ALoCoQkZuMLbyeyKihz7d84XNe+Oq6Ii80AeEVrI0klq8d8qZ55xvKwb7W8RFxsUwLv7KnQzKnLO X-Received: by 10.194.243.36 with SMTP id wv4mr3883282wjc.83.1413281166591; Tue, 14 Oct 2014 03:06:06 -0700 (PDT) Received: from [192.168.8.194] ([80.168.34.50]) by mx.google.com with ESMTPSA id q10sm19605074wjq.35.2014.10.14.03.06.05 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Oct 2014 03:06:05 -0700 (PDT) Message-ID: <543CF595.6030107@jonstirling.co.uk> Date: Tue, 14 Oct 2014 11:06:13 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: internals@lists.php.net References: <32b8315ede38cd03ad4a7ab4497397e9@mail.gmail.com> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] RFC: PHP 7.0 timeline From: phoenix@jonstirling.co.uk (Jonny Stirling) Hi: On 14/10/14 10:48, Julien Pauli wrote: > Makes sense, however, we should absolutely be sure to integrate every > BC idea we'd like to into 7.0 > If not , one will have to wait something like 10 years if we don't > allow BC breaks in 7.X minors. > I have to agree with Zeev that we shouldn't wait for things that might or might not pop up, but keep track of any and act as appropriate if / when they do. I know that's not what you're getting at, just wanted to emphasize the point. Providing a formal list of what is being included / excluded from 7.0 in this regard may also be useful so there is no confusion later down the line. At the same time, which I think has been discussed before, perhaps it's time for a regular major release cycle (regular as in x (2-3?) years) so that there is a timescale for when new changes (or ones that might be intentionally or unintentionally missed / skipped for this major) that wouldn't be allowed in minor releases can be proposed / written against? Apologies for strictly being off-topic. Ta. Jonny.