3 ms·
You know that there is a point to it, right? Now there are always 4 versions: fresh nightly builds, dev, beta, and stable. Every ~6 weeks dev becomes beta and b
by ahoge 13y ago
You know that there is a point to it, right? Now there are always 4 versions: fresh nightly builds, dev, beta, and stable. Every ~6 weeks dev becomes beta and beta becomes the new stable version. This way you get a higher degree of parallelization. There is no global feature or whatever freeze. New stuff is added all the time.
The version number is now basically just a step counter.
- BlackDeath3 13y agoCan't wait for Firefox 150!
- ahoge 13y agoI know you tried to be funny, but this "150" actually means something very specific. It's +125 of those steps. That's way more meaningful than +7 major releases. Just look at other software. Sometimes it takes 1 year. Sometimes 6 or even longer. Sometimes the changes are very minor or purely cosmetic. Sometimes the changes are very drastic. Sometimes it's even a complete rewrite. I don't see how that's any better. Basically, it just means that someone thought it would be a good idea to increase the major number by one.
- BlackDeath3 13y agoWhat I said doesn't imply that I find the idea silly, but "Firefox 150" does indeed sound silly to me. However, what you say seems to hinge on the idea that each of Firefox's steps are consistent in their impact. Is that true?
- ahoge 13y agoOf course there is some variation. There are always some bigger features which take their sweet time. However, there is always a constant stream of smaller fixes and improvements. Also, if there are ~86 releases per decade, those features and improvements are of course far more evenly spread compared to some product which only released 4 versions in the same time span. (IE6 was released in 2001 and IE9 in 2011.)