Re: [RFC] Deprecations for PHP 7.2
| From: | Christoph M. Becker | Date: | Sat, 19 Nov 2016 18:16:15 +0000 |
| Subject: | Re: [RFC] Deprecations for PHP 7.2 | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-97064@lists.php.net to get a copy of this message | ||
On 19.11.2016 at 18:56, Marco Pivetta wrote:
> On Sat, Nov 19, 2016 at 6:42 PM, Kalle Sommer Nielsen <kalle@php.net> wrote:
>
>> So to answer your question in a short without much more rambling: I
>> think we should deprecate in x.z, then remove in x.z+1 depending on
>> the feature, if we say "Oh let's remove this in the next major",
>> chances are that major won't even be branches for years, and at that
>> time, it could be forgotten.
>
> That will end up breaking the "expected" (because it's not that way anyway,
> but almost) SemVer approach, diminishing the trust from consumers in any
> kind of upgrade.
> Most of the current open-source libs out there are trying to push for
> SemVer - having PHP not following that seems like a huge mess to me.
Our release process[1] explicitly forbids breaking userland API between
x.y.z and x.y+1.z.
[1] <https://wiki.php.net/rfc/releaseprocess>
--
Christoph M. Becker