Rex wrote:
Firefox went from version 4 to version 5 in less than 2 months - in imitation of Google Chrome, who seem to be incrementing the version every other week. Please tell me Seamonkey isn't going to do the same thing so that by the end of the year we're up to version 3.5 or 4, and 5 by next year. Last week I updated to 2.1, and now barely a month later you're on 2.2, and looks like 2.3 is a few weeks away..compared to when 2.0 debuted last September and went on up to 2.0.14 for the minor fixes.
Have you ever seen gas(oline) price wars between competing pumping stations in a neighbourhood? :) Though in the case of SM they do have the justification of needing to track FF and TB.
I can see 2.1 has major new features and changes relative to 2.0x, but what about between 2.1 and 2.2? Shouldn't this be a minor update to 2.1?
Well really what does the label attached to the release matter? What matters is the lack of stability and requirement for frequent patch releases, whatever version label gets attached to them.
I have the same gripe as others here - broken extensions. All this while I was happily using QuoteColors, Tagzilla, and several more, now they're all broken.
Well now, and how are the equivalent extensions and plugins faring for the new versions of FF and TB??? Have those Mozilla product development teams managed to better persuade the extension writers to coordinate with their new versions? It is, after all, the extension writers/maintainers who have to make the appropriate changes to their products. Of course one can argue some about the details, of needed/gratuitous changes to the interface requirements, ... , and coordination with these developers. There have been some postings here about how to make some of the current version of plugins work with the new SM. -- Rostyk _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
