Comment on Firefox 140 Brings Tab Unload, Custom Search & New ESR
squaresinger@lemmy.world 1 day agoI haven’t read too much into the topic, but I wouldn’t be surprised if this was as much a marketing decision as well as a developer one.
Version numbering has no implications on development. Firefox released just as frequently before, just that they didn’t increase the major version that often.
audaxdreik@pawb.social 1 day ago
I understand that, so then why change it?
This does not appear to be true.
That blog post has an aura of marketing speak around it.
Version numbering has no implication on development and doesn’t even need to align internally and publicly, so somewhere a conscious decision was made to do it this way for “reasons”. I conjecture those reasons are at least partially due to marketing. Is this not fair?
EON_GuG@lemm.ee 1 day ago
Well, normally, when people see a larger version of a software, they think it’s more secure, modern, better, and other things.
For example, not all Chromium projects follow version nomenclatures. Vivaldi, Opera, and Brave all use their own version nomenclatures.
squaresinger@lemmy.world 1 day ago
Read again. I quoted something along the lines of “just as much a development decision as a marketing one” and I said, it wasn’t a development decision, so what’s left?
Why don’t you take a look at the version history instead of some marketing blog post? www.mozilla.org/en-US/firefox/releases/
Version 2 had 20 releases within 730 days, averaging one release every 36.5 days.
Version 3 had 19 releases within 622 days, averaging 32.7 days per release.
But these releases were unscheduled, so they were released when they were done. Now they are on a fixed 90-day schedule, no matter if anything worthwhile was complete or not, plus hotfix releases whenever they are necessary.
That’s not faster, but instead scheduled, and also they are incrementing the major version even if no major change was included. That’s what the blog post was alluding to.
In the before times, a major version number increase indicated major changes. Now it doesn’t anymore, which means sysadmins still need to consider each release a major release, even if it doesn’t contain major changes because it might contain them and the version name doesn’t say anything about whether it does or not.