On Wed Sep 21 09:57 AM, Matthew Weier O'Phinney wrote: > > > It then reverts is_a() back to the previous behavior, and clarifies > > the documentation. > > > To respect the release RFC, we shouldn't introduce a new BC break > (breaking behavior with something already released). >
That's just a ridiculous statement, the release rfc should have been respected in the first place. Can you explain to me where in the RFC it explain that if "the new behavior is more correct" then a minor release can break BC? This whole story smells like bad PR, this is a new *feature* that breaks BC and not a bug fix. Either way, I don't have a strong opinion on reverting the change or not, but it should be *acknowledged* today that this "fix" did not belong in 5.3.8. If that's not done, then I have no hope for the future releases from PHP.net I'll look at package maintainers or companies with a more rigorous release process, it's that simple. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
