Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:102700
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmx.de designates 212.227.17.22 as permitted sender)
To: Nikita Popov <nikita.ppv@gmail.com>, Zeev Suraski <vsuraski@gmail.com>
Cc: Sara Golemon <pollita@php.net>, Kalle Sommer Nielsen <kalle@php.net>,
 Internals <internals@lists.php.net>
References: <CAF+90c_+GZNrV1SC9q=Y3C=L3LMnoXX7J3zK6=kS9-sMXHZZow@mail.gmail.com>
 <CAJW__o3BsiUoMwxhwPwBwY+OTPt1f=O6aQsHBot-Dat3MRCBpg@mail.gmail.com>
 <CAF+90c_x5ad+oAdPRKaEasMGAUyK+UELHnPEai-aOAPquKVySA@mail.gmail.com>
 <5153610d-abed-b21a-ec55-56d967128cae@gmail.com>
 <CAJW__o3smiKaCQOFSYqtQzPZJb2=iuR0RojWqshoOadFD7-vHg@mail.gmail.com>
 <CAF+90c8z-r4aL8ZVOCU+3V4tc3R2dhWXbDgXc+sOy3Cnb6i=sg@mail.gmail.com>
 <CAJW__o0EEABZDzg9CbPgRfY5u_DUL4+fUbbn3VDzuK0nseeiOQ@mail.gmail.com>
 <CAJW__o1wjqVNgsbGQvKNYBdT8NUa+aJjiOsRToP6OcnQybxN_w@mail.gmail.com>
 <CAF+90c8v15GXSCofiq4_s51_+fQguHgJF=4OVGiKOYF1BgkaCA@mail.gmail.com>
 <cfc6ed92-3062-8026-ac2d-c43061918ef9@gmx.de>
 <CAESVnVr0oB2vF793hLqi6q2ELOJMJ6mjpp5B_ZsXj2WEVNmE9A@mail.gmail.com>
 <017101d41815$95118440$bf348cc0$@gmail.com>
 <CAF+90c8Y4PAi+PCGnHV_xf3_3HaY8yc8Ww3nyur88UqX_xP+Kw@mail.gmail.com>
Message-ID: <c397cf94-a713-6f33-0696-5e35db3dbae5@gmx.de>
Date: Tue, 10 Jul 2018 12:35:37 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
 Thunderbird/52.9.0
MIME-Version: 1.0
In-Reply-To: <CAF+90c8Y4PAi+PCGnHV_xf3_3HaY8yc8Ww3nyur88UqX_xP+Kw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: de-DE
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] [RFC] Deprecations for PHP 7.3
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 10.07.2018 at 09:36, Nikita Popov wrote:

> To make sure there are no unreasonable expectations involved in this
> decision: If this feature will not go into PHP 7.3, then it will in all
> likelihood go into PHP 7.4 instead. I think I can safely say not just on
> behalf on Bob and myself, but also on behalf of the wider PHP community,
> that we are not willing to sit on this feature for 2.5~3 years until a
> hypothetical PHP 8, even though it is essentially ready *now*. Of course,
> this is not my decision to make, but as Sara put it, that's the writing on
> the wall. By deciding not to include this in PHP 7.3, we are essentially
> making an implicit decision that PHP 7.4 is going to be a relatively
> ordinary feature release rather than a deprecation-only one. (Which is fine
> by me really, I don't like the idea of a release that's all stick and no
> carrot.)
> 
> Finally, given the current situation where we have a whopping five (!!)
> RFCs with votes ending the day before feature freeze, I'd say postponing
> the schedule is a good idea even without any consideration to typed
> properties. Just landing something like the comparison overloading RFC on
> the day of feature freeze is not going to be pretty. We are quite obviously
> rushing things right now, and I don't think keeping to some otherwise
> arbitrary date is worth that.

Good point!  Thus, I suggest to put in *one* additional alpha (i.e.
postponing feature freeze by two weeks to 2018-07-31) in any case, have
the vote on “Typed Properties” starting soon with explicit options which
version these should be merged into, and if there will be an option to
target PHP 7.3, *and* the voters decide it should go into PHP 7.3, to
insert yet an additional alpha5.

Anyhow, I strongly suggest to amend our voting and release rules to
avoid such situations in the future.  Ending any vote one day or a few
days before feature freeze should simply not be allowed (unless the RFC
targets another version).  And there should be clear rules which
circumstances warrant or allow to postpone feature freeze, and who's
decision that is.

-- 
Christoph M. Becker