4 ms·

This 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 versioni

This 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 ago
Except 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 ago
  5.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 ago
    I 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

rjknight 13y ago

Except 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 ago
5.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 ago
  I 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