-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Using 2 patches:
https://gist.github.com/smalyshev/4d8435b7993bef80c0ed https://gist.github.com/yohgaki/c3783b22bae9dcb78d69 $ /work/build/php56/sapi/cli/php /usr/bin/phpunit - --include-path=/usr/share/pear . PHPUnit 5.1.4 by Sebastian Bergmann and contributors. ..................SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS........... 65 / 66 ( 98%) Time: 53 ms, Memory: 6.50Mb OK, but incomplete, skipped, or risky tests! > Thanks for all the investigation (as well Remi, Stas and everyone). > At first glance last week, as for me, it looked like OK to keep at > least the 7.0 part, as the breach was only > concerning the unit tests but unlikely the actual web > functionality. While it is good to > have improvements and hardening on the unclean behaviors, the area is critical and should > be kept stable in stable branches. Right now, it seems that the patch can have unexposed impacts. > > I would like also to remind that we're now quite short in time as > finals are planned for the next week. With this in mind, IMHO it's > better to play safe and revert 5.6 and 7.0 > to the previous state before this change. Or at least, don't > release these patches in > the upcoming finals, but keep improving and fixing BC breaches in dev branch and re-evaluate > the status in the next possible RC. Right. Or, we need a RC2. (which means RC2 this week + slip finale by 1 week) Remi -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlaofKwACgkQYUppBSnxahiMcgCg3EBIB+FgfGKtTJxX4MgAfibb nT8AoOBkB1e0GZJHoJOGSJ2JOBs+7XRX =oBfC -----END PGP SIGNATURE----- -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
