Standards Make Rapid Software Releases Workable 97
jfruhlinger writes "There was a bit of a kerfuffle when the Mozilla Foundation's community coordinator brushed aside concerns from enterprises that Mozilla's rapid release schedule clashed with organizations' need to carefully vet software upgrades. One thing that could bridge the gap between these worldviews is a widespread adoption of open standards. After all, if IE 6 dealt with web pages in a standard way, it wouldn't have been so painful to keep it around as long as it lurked on many corporate desktops."
Re:Version numbers (Score:5, Informative)
Firefox's release schedule isn't any more "rapid" than it was before just because they now change major version number instead. It's just taking away the real problem and trying to be push your software to the version numbers that long term projects like IE and Opera have got over the years. Same problem with Chrome.
Tell that to an addon developer, where the churn of compatibility-breaking changes (many for no apparent reason) is causing a real headache.
There is a promised SDK to land sometime this summer. We'll see if Mozilla can deliver a stable API for more than a few months.