On Thu, Mar 19, 2015 at 6:49 PM, Zeev Suraski <z...@zend.com> wrote: > > On 19 במרץ 2015, at 19:40, Dan Ackroyd <dan...@basereality.com> wrote: > > > > You are being dumb here as well. We try to avoid breaking code in > > point releases. This BC break can only be done at a major version. > > Technically, we're not allowed to move from from a working feature into a > removed one without a deprecation phase. >
I don't think this is true. There is no requirement for us to deprecate something before we remove it. Deprecation is a courtesy to our users in cases where a heavily used feature is being dropped. Realistically most people consider E_NOTICE to be a higher error level than E_DEPRECATED. If somebody is willing to suppress the notices this currently generates, chances are very high that deprecations are suppressed as well. I don't see any release process issues with dropping this without deprecation. (But I'm still -1 on the change, because I don't see why we'd suddenly want to change this one relatively unimportant notice to be fatal while leaving everything else alone.) Nikita
