On Sat, Nov 27, 2010 at 12:50 PM, Karoly Negyesi <kar...@negyesi.net> wrote: > Hi, > > I am reading the 5.4 vs 7.0 debate. And, here's something I really > need to follow up on: "We should reserve major versions for BC breaks. > Just like we've always done". If that's what you've always done then > it's not PHP I spent practically every awake minute in the last seven > or so years. > > If backwards compatibility break would mean a new PHP major we would > be in somewhere PHP 43 or something :D > > Seriously. From PHP x.y.z to PHP x.y.z+1 > tl;dr the PHP developers have a false belief in not breaking backwards > compatibility in minor releases.
No, but there are way too many possibilities to break things without us even noticing it. That's why we proposed the release process and rules RFC: http://wiki.php.net/rfc/releaseprocess which clearly disallow BC breaks in bugs fixes releases. Given that we have a way to actually test releases efficiently. We constantly work to improve QA as well, it is also why I asked for apps and frameworks authors or QA lead to get in touch to see how we can have your tests valid our changes. Cheers, -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
