Hi Anatoliy,
I can't see the NEWS entry in the PHP-5.4 or PHP-5.3 heads:
http://git.php.net/?p=php-src.git;a=blob_plain;f=NEWS;hb=refs/heads/PHP-5.4
http://git.php.net/?p=php-src.git;a=blob_plain;f=NEWS;hb=refs/heads/PHP-5.3
I can see it in NEWS from the 5.3.12.tar.bz2 bundle.
This all reinforces that the PHP NEWS updating process is one of my pet peeves.
In any case, the backward compatibility break isn't mentioned - this is the
critical
thing that should be mentioned to help end users.
Chris
On 05/04/2012 03:57 PM, Anatoliy Belsky wrote:
Chris,
it's already in the news
http://git.php.net/?p=php-src.git;a=blob;f=NEWS;h=d26ffea8ab357a44e37044193c8b316dfaa61662;hb=704bbb3263d0ec9a6b4a767bbc516e55388f4b0e
Regards
Anatoliy
On Fri, 04 May 2012 15:19:31 -0700
Christopher Jones<christopher.jo...@oracle.com> wrote:
On 05/04/2012 03:10 PM, Sean Coates wrote:
What are the options for reverting this fix (while keeping security)?
Thanks for the help on this, Anatoliy and Chris.
In my opinion, it is too late to revert the new behaviour.
This really should never have gone into .11 in the first place. The damage is
done; let's not make it worse.
Anatoliy,
Do you recall why bug 61504 isn't in NEWS? Can you make sure some kind of
entry in
NEWS mentions the change?
Thanks,
Chris
--
christopher.jo...@oracle.com
http://twitter.com/#!/ghrd
--
christopher.jo...@oracle.com
http://twitter.com/#!/ghrd
--
PHP CVS Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
