Re: BC break in 5.4.29 and 5.5.13
| From: | Pierre Joye | Date: | Tue, 17 Jun 2014 21:15:57 +0000 |
| Subject: | Re: BC break in 5.4.29 and 5.5.13 | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-74959@lists.php.net to get a copy of this message | ||
On Tue, Jun 17, 2014 at 8:07 PM, Ferenc Kovacs <tyra3l@gmail.com> wrote:
> I agree with you, however the facts shows differently:
> http://php.net/ChangeLog-5.php#5.5.11
> OPCache: Added function opcache_is_script_cached().
Fact that some does whatever they want at wishes is bad, I agree.
> And even the releaseprocess rfc is written in a way, which implies that
> introducing new features are not considered as BC breaks:
>
> https://wiki.php.net/rfc/releaseprocess
>
> x.y.z to x.y+1.z
>
> Bugfixes
> New features
> Extensions support can be ended (moved to pecl)
> Backward compatibility must be kept
> API compatibility must be kept (userland)
> ABI and API can be broken (internals), src compatibility should be kept if
> possible, while breakages are allowed
But no new features in released branches.
--
Pierre
@pierrejoye | http://www.libgd.org