4 ms·
> Numbers aren't intrinsically important True, so yeah I stand corrected about that. Now, can we tell Mozilla this and get off this ridicul^H^H^Hrapid release
by lucb1e 13y ago
> Numbers aren't intrinsically important
True, so yeah I stand corrected about that. Now, can we tell Mozilla this and get off this ridicul^H^H^Hrapid release cycle?
- shock 13y agoI actually prefer it this way rather than a big code drop every couple years.
- acdha 13y agoThis release cycle is great: it's not quite as fast as Chrome but it means that I can start using features for 90+% of the Firefox-using public within months of release rather than years.
- PavlovsCat 13y agoWell, the version numbering system has no bearing on the frequency of updates Still, I don't see the difference between 1.0/1.01/1.02 and 1.0/2.0/3.0 -- it's still "3 versions". I say version numbers are bullshit, codenames doubly so.. just make it the release date or build number and be done with it. Automate it, and let no human ever think about it again. It's just an identifier for a specific changelog entry after all, and has no meaning by itself.
- pygy_ 13y agoUpdates are automatic, and understated in the UI. Version numbers are still useful as literal milestones (well, allmost... it would be 6-weeks-stones, but no such thing exists).
- acdha 13y agoThat's why I said “release cycle” – moving from numbers to “when it's ready” was definitely the key part. The trick was breaking the tyranny of significant numbers where people would hold off until they had enough features to be worthy of a major release.