Re: No plans to change the version number scheme
Ron Hunter <[email protected]> Tue, 23 Aug 2011 18:41:36 -0500
| Newsgroups | gmane.comp.mozilla.ui |
|---|---|
| Message-ID | <[email protected]> |
On 8/23/2011 5:51 PM, Matt Brubeck wrote: > On 08/23/2011 03:16 PM, Adam Kowalczyk wrote: >> Could you please elaborate on the decision to preserve the current >> numbering scheme? The idea to incorporate year in the version number was >> an interesting proposal that seemed to enjoy a lot of support in the >> community, as it could potentially alleviate some of the tension and >> misunderstandings around the new release process. > > I'm open to date-based versioning and I know a lot of other Firefox > developers/designers/contributors also think it might be a good idea. > But personally I don't think we should do it yet, because: > > 1) If users keep noticing Firefox versions and updates at all, then we > have much bigger problems. For rapid release to serve our users well, we > must get to the point Chrome is at where only very attentive > developer-types even notice when the version changes, and 95-99% of > users don't even notice when an update is installed. This is why almost > no one is complaining about Chrome's versioning system. > > Firefox is not there yet; we still have tons of work to do on add-on > compatibility and silent (by default) updates. When it gets there, then > the numbering scheme won't matter any more. Or if we can't get it there, > we'll have to change our process in much bigger ways than just version > numbering. > > 2) While there are also real practical causes of user pain associated > with rapid release, another cause of user pain is just the fact that > change is always confusing. Adding more change this early in the process > will make this part worse rather than better. I think we should consider > changing the version scheme, but not right away. > > Since Firefox 12 is scheduled for mid-2012, that could be an ideal time > to switch from milestone- to date-based versions, if we decide to do so. :) That's because Chrome updates silently, so users don't know that an update has happened, unless they happen upon a new feature. I consider this a negative factor as it doesn't make a user aware of the efforts that have gone into the new features, nor does it highlight their usefulness to the user. Most of the Firefox users I have heard from consider Google's method a bit 'underhanded'. But then I deal with power users, who are going to want control of updates, and want to know but new features. I am sure that most users just really don't care. I sincerely hope that Firefox doesn't become the browser of choice for those who don't care...