4 ms·

I mean this only makes sense in a world where everyone uses semantic versioning (and the project doesn't seem to indicate this anywhere). Versioning numbers, pe

by dvt 4y ago

I mean this only makes sense in a world where everyone uses semantic versioning (and the project doesn't seem to indicate this anywhere). Versioning numbers, per se, don't really have any bearing on application stability.

mccorrinall 4y ago
Even when using semver it just means that there were never any major breaking changes. React is also still 0.x :)
- dvt 4y ago
  Interestingly, being `0.y.z` as a major released version (e.g. not in development or a release candidate) does seem to break semver[1], but I do realize it's more of a guideline and no one really cares: > Major version X (X.y.z | X > 0) MUST be incremented if any backwards incompatible changes are introduced to the public API. It MAY also include minor and patch level changes. Patch and minor versions MUST be reset to 0 when major version is incremented. [1] https://semver.org/ https://semver.org/
  - bitdivision 4y ago
    For versions < 1.0.0 this does not apply: > Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.
- riquito 4y ago
  > React is also still 0.x :) It moved away from 0.x around 6 years ago
  - lelandfe 4y ago
    https://github.com/facebook/react-native/releases https://github.com/facebook/react-native/releases React Native is still 0.x, since 2015!
  - mccorrinall 4y ago
    Oh, heck, you are right! I mixed up react and react native.
- deleted 4y ago
  [deleted]