It is not, at least not in the sense that you're suggesting. Firefox does not make an inordinate fuss over its version numbers - pretty much only to the extent required to encourage people to upgrade quickly. Google does not make much of a fuss about version numbers at all.
It is a strategy to compete with Google Chrome by rolling features out much more quickly. If you've lived with the stable Firefox release 3.6 through its lifecycle, rather than upgrading to the betas for 4.0, you've had the same feature set for close to a year. Chrome users, on the other hand, have continued to get new features on a regular basis.
Firefox is trying to change that and match Chrome's development style by pushing updates out more quickly.
Beyond Firefox 4.0: Handling an accelerated development cycle
Posted Mar 11, 2011 15:30 UTC (Fri) by sorpigal (subscriber, #36106)
[Link]
Then why not go with 4.1, 4.2 and 4.3 instead of 5, 6 and 7? If it doesn't matter and users don't care and it's not about marketing how about continuing a practice that makes sense and makes me happy?
Beyond Firefox 4.0: Handling an accelerated development cycle
Posted Mar 11, 2011 22:15 UTC (Fri) by anselm (subscriber, #2796)
[Link]
I say they want to catch up with Internet Explorer, which is around version 9 these days.
Beyond Firefox 4.0: Handling an accelerated development cycle
Posted Mar 14, 2011 10:00 UTC (Mon) by jezuch (subscriber, #52988)
[Link]
And end up like the Linux kernel, at (for example) 4.38, without a reason to bump the major number ever again? In the world of "cadence" and incremental updates the <major>.<minor>.<micro> versioning scheme is more and more obsolete.
Beyond Firefox 4.0: Handling an accelerated development cycle
Posted Mar 14, 2011 13:49 UTC (Mon) by nix (subscriber, #2304)
[Link]
I'd call it less(1) and less(1) obsolete. (What's that at now? Version 441?)
Beyond Firefox 4.0: Handling an accelerated development cycle
Posted Mar 14, 2011 14:02 UTC (Mon) by vonbrand (subscriber, #4458)
[Link]