Re: Is the "No BC Breaks in Minor Releases" policy enforceable?

On 13/06/2016 10:35, Joe Watkins wrote:

    Backward compatibility is important. Also important is the long term

goals for PHP, or at least for this major version of PHP: The goal is to make Zend so efficient that generating machine code from user code becomes a deployable solution.

OK, that's an interesting bit of background, which might explain why Dmitry seemed in a hurry to get this in place. I was aware of the discussion of performance, but not the background "long-term goal". Is there a roadmap somewhere that describes this, or any background discussion of doing this within the 7.x series, rather than planning for 8.0?

    I can be wrong, might be ... it doesn't really matter, the majority

has spoken. It is only my concern that the change is documented properly.

This is my main concern, also. The RFC is very brief, and the discussion period was artificially shortened, and I think the implications to the BC policy make this RFC more important than Dmitry assumed. Having a documented reason why a BC break was accepted in this case will help to set expectations in the future. Ideally, this could lead to a revised policy with BC guidelines that actually match the current reality of the project, which the existing RFC does not seem to do. Regards, -- Rowan Collins [IMSoP]