On Mon, 2014-01-27 at 21:15 +0100, Anatol Belski wrote:
> https://wiki.php.net/rfc/size_t_and_int64
It is my understanding that part of the reason for the release workflow
RFC was that if patches miss the mark they don't have to wait for long
till the next release comes.
In this case here we have 5.6.0alpaha1 out. Adding a major API change
touching each and every file can't be added to 5.6 anymore.
Also the release process RFC says
x.y.z to x.y+1.z
[...]
ABI and API can be broken (internals), src compatibility
should
be kept if possible, while breakages are allowed
This rule contains many things that "can" and "should" and thus is open
to interprettation. In my interpretation this rule is meant to allow
small changes, affecting only few extensions and where it would be
stupid to defer the.
I think adding this patch to 5.x therefore would be quite some bending
of that rule and that combined with the fact that it is late makes me
believe that proposing this for 5.6 is illegal.
johannes