3 ms·
Yes, see this[0] for example. If memory serves me right, the TLDR is that the more typical release management system can cause certain features to not be relea
by asymmetric 7y ago
Yes, see this[0] for example.
If memory serves me right, the TLDR is that the more typical release management system can cause certain features to not be released as soon as they're ready, because other features that should go in a major release are not ready yet.
By removing the semantic component of release numbers and releasing often, this does not happen. Feature ready -> shipped soon.
[0]: https://hacks.mozilla.org/2019/09/moving-firefox-to-a-faster-4-week-release-cycle/ https://hacks.mozilla.org/2019/09/moving-firefox-to-a-faster...
- mythmon_ 7y agoI'd say that Firefox versions are mostly a unit of time now, since they aren't generally semantically meaningful in the way semver is. While working on Firefox, we often make plans that are delineated not in weeks, months, and quarters, but in Firefox releases and the nightly/beta/release cycle associated with them.
- retonom 7y agoWell, actually it was introduced after Chrome switched to this same model. So it looked like Chrome is advancing faster because they released a new major version every few weeks and it got more press. I suppose that's why they really switched. If it would be just a matter of the management system you'd better adapt the system instead of version numbers. Anyway, after so many "major" releases the press has died down. So what we have now is version numbers that are quite meaningless because you can't pin major changes in the architecure to version numbers anymore.