4 ms·
They added coroutines in a minor number patch. wat.
by angersock 13y ago
They added coroutines in a minor number patch. wat.
- pilif 13y agoJust as rails has added the asset pipeline in a minor number patch. Or as ruby changed to unicode with 1.9. Or as python added a whole new syntax for exceptions with 2.6. As with many other languages, incrementing the minor number usually means quite big changes while more or less keeping backwards compatibility. Changing the major number is something that's done when backwards-compatibility is hugely affected. The exception is probably ruby which greatly broke backwards-compatibility with 1.9 (unicode) and mostly just changed internals with 2.0
- angersock 13y agoOh, I'm not about to hold up ruby or python as shining beacons here--though I will smugly admit that the rubyists seem to be pretty fast at updating their gems. Still, it's weird practice nonetheless, right?
- pilif 13y agoActually, I think it's fine for languages: Backwards-Incompatible change? Increment Major version Many new features, but (largely) backwards compatible? Increment Minor version. Bugfixes? Increment Patch. I think this also perfectly maps to Semantic Versioning (http://semver.org/ http://semver.org/)
- coldtea 13y ago>Still, it's weird practice nonetheless, right? No, it depends on the versioning number scheme. Not all schemes mean the same thing with major/minor/minorer.
- rjknight 13y agoPHP's versioning has generally been a bit weird since the abortive PHP 6 project. PHP 6 was meant to be the version that implemented full unicode support, but this proved to be very difficult, with the result that major new features had to go into the 5.x branch while 6.x remained in development (which, I guess, it still is). 5.3 added closures and 5.4 added traits, so adding coroutines in 5.5 is not inconsistent with past behaviour. I guess it's sort-of like how every version of OSX is 10.x, even though there have been massive changes between 10.0 and 10.8; it makes more sense to think of 10.8 as being 'OSX version 8'. Likewise 'PHP5' has been around for so long that nobody really looks at the major version number any more.
- agwa 13y agoIt seems like every major software project reaches a point where the major number just stops changing. Linux too - it became clear that it was going to be 2.6.X.Y forever, so they renumbered to 3.X.Y to make the version string shorter. I guess it's a sign of maturity: the project has reached a solid codebase with good development practices so there won't be any more overhauls that warrant a major number increase.
- rjknight 13y agoChrome is a good counter-example, but I agree that it's rare.
- tomku 13y agoI view Chrome (and Firefox now) as essentially having "Chrome" and "Firefox" as their major version numbers, if that makes sense. It's so unlikely that they'll break compatibility that any such break would probably result in a completely new product/branding.
- dave1010uk 13y agoThis is standard in PHP's release process [0]. New features are fine, as long as they don't break backwards compatibility. This is the same as semantic versioning [1]. [0] https://wiki.php.net/rfc/releaseprocess https://wiki.php.net/rfc/releaseprocess [1] http://semver.org/ http://semver.org/
- rjknight 13y agoExcept that PHP's 'minor' version changes do break backwards-compatibility: http://www.php.net/manual/en/migration55.incompatible.php http://www.php.net/manual/en/migration55.incompatible.php http://www.php.net/manual/en/migration54.incompatible.php http://www.php.net/manual/en/migration54.incompatible.php http://www.php.net/manual/en/migration53.incompatible.php http://www.php.net/manual/en/migration53.incompatible.php http://www.php.net/manual/en/migration52.incompatible.php http://www.php.net/manual/en/migration52.incompatible.php As someone who has maintained open source software for PHP, the idea that there's backwards-compatibility between different versions of 5.x is not really correct. From a features perspective I think this is a good thing - PHP needs to move forward - but it's wrong to say that PHP entirely follows the SemVer standard.
- robryan 13y ago5.x releases are bigger than the versioning suggests, the 5 series is likely 10 years old now? Breaking changes in each is fine.
- rjknight 13y agoI agree. It's just not what the SemVer standard[1] says. To be honest, I don't really care about following SemVer exactly. And PHP does follow SemVer if you pretend that the major version number doesn't exist, and the minor version number is really the major one (hence we're just seeing the release of version 5.0 of 'PHP5', rather than 5.5.0 of 'PHP'). This is all pretty easy to understand and it's not a bad way of doing things, but claims that PHP follows SemVer are incorrect and will cause confusion. [1] http://semver.org http://semver.org
- coldtea 13y agoNot all versioning schemes are the same. You have to know what the versioning scheme means in a particular project to judge that. The minor number in PHP does not mean bugfixes and small stuff only, as does in some project. The second even minor-er (!) number (.x.y) is for that. PHP has always added tons of stuff in .x releases (closures are another example). Python also adds major features in minor versions all the time. You can find similar grand changes between 2.x releases.