Hacker News new | past | comments | ask | show | jobs | submit login

Unfortunately Rust is not actually using semver, which I always found confusing because they seem to be in support of it, and they even include a semver library in the core distribution. If they were following semver, this release would be version 0.10.0 (notice the patch version).

The point of semver is to stick to a standard, instead of every project deviating from common practice in subtly incompatible ways.




Right, we didn't really "adopt" semantic versioning until sometime after 0.1, and so we've never really gotten into the habit of including the patch revision (and with one exception, we've never issued a patch for any of our unstable releases anyway).

Here's the issue for getting us to adhere to semver proper: https://github.com/mozilla/rust/issues/11396


There's an open issue for this: https://github.com/mozilla/rust/issues/13289


> If they were following semver, this release would be version 0.10.0 (notice the patch version).

Actually, since they are doing backwards incompatible changes in every release, this version would be more like 10.0.0.

They are deviating from semver for now, I hope they get on it properly for 1.0.0 and beyond.


You are allowed to make breaking changes at any time if your major version is zero.


Right, because the semver "standard" is inconsistent in that particular way.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: