To view parent comment, click here.
To read all comments associated with this story, please click here.
Version numbers are extremely important, especially for developers. How do you know which javascript function isn't working in which browser version? Why does this add-on work in Firefox 6, but not in Firefox (n+3) which came out 4 months later?
Do I need to test my javascript in Firefox 4, 5, 6, 7, 8, and Chrome 10, 11, 12, 13, 14? To cover all versions released in the last 6 months?
I'm sick of all of it. In a corporate environment, you want slow, measured version number changes. You can't just keep upgrading for the sake of upgrading every 6 weeks.
There should be a long term support version of firefox next year. For now, is it possible for you to stay with Firefox 3.6 until it nears the end of support and then go with long term support versions?
https://wiki.mozilla.org/Enterprise/Firefox/ExtendedSupport:Proposal
I am not a fan of the new version numbering, however, in my experience the quality of firefox has increased quickly in recent months.
Edited 2011-11-09 17:41 UTC
Do I need to test my javascript in Firefox 4, 5, 6, 7, 8, and Chrome 10, 11, 12, 13, 14? To cover all versions released in the last 6 months?
I'm sick of all of it. In a corporate environment, you want slow, measured version number changes. You can't just keep upgrading for the sake of upgrading every 6 weeks.
Version numbers are not important but what is is what changes have occurred. Long, slow version changes are especially good for people who are too lazy to pay attention to the changelog.
Shouldn't you just test for the feature? Either give a warning if the browser doesn't support the feature or have a backup feature that simulates the behavior with older techniques. I am not a webdeveloper so correct me if I'm wrong.




Member since:
2008-08-19
Other way around, actually. Mozilla have decided they no longer care about version numbers at all. There's no real marketing around it - no big announcements of an 8.0 release. Just another quiet update that happens to change a number that's not even visible unless you go to the About screen...