16 ms·
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
by yepguy 13y ago
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.
- Tuna-Fish 13y ago> 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.
- yepguy 13y agoYou are allowed to make breaking changes at any time if your major version is zero.
- mcguire 13y agoRight, because the semver "standard" is inconsistent in that particular way.
- psquid 13y agoYes, but intentionally so - 0.y.z versions are meant to allow you to more-or-less try stuff out without inflating version numbers, with the 0. reminding users that they shouldn't consider it ready yet if they need API/feature stability.
- kibwen 13y agoRight, 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 https://github.com/mozilla/rust/issues/11396
- brson 13y agoThere's an open issue for this: https://github.com/mozilla/rust/issues/13289 https://github.com/mozilla/rust/issues/13289