Justin Wood (Callek) ha scritto:
On 7/16/2011 10:05 PM, Graham wrote:
Once again, I thank the Mozilla and Seamonkey teams for all their
efforts: the web and all its browsers are much better for their efforts;
even IE has improved by leaps and bounds because of Firefox. I won't be
along for the ride, but I will keep an eye open, and may be back one day.
Thank you for your constructive comments.
While many of us (SeaMonkey Council) share your concerns with the Rapid
Release Cycle, the brunt of the matter is that us, as a Mozilla Platform
Consumer, are tied to the platform schedule -- unless we want to expose
you, our users, to security issues. If the situation on that level
changes, we can -- and will -- revisit our release schedule plans.
While I do not feel that chrome is a better choice for you as a user, I
do not condemn your choice to leave us for the time being, I just hope,
one day, you will be back :-)
I actually believe that SM is the Mozilla application which best reacted
to the rapid release cycle: instead of just changing the version number
to the same as firefox, as Thunderbird did, SM kept the "2" major
version number, and only uses the second number to distinguish minor
releases.
So since, if I've understood correctly, passing from SM 2.1 to 2.2 and
so on is like it was passing from 2.0.1 to 2.0.2, couldn't add-on
developers usually just put a generic 2.* max version, and still be sure
that their extension will work, just as it happened by using a max
version of 2.0.* with the old release cycle? There will sure be some
exceptions, but I think that could work for many (I've seen that many
extensions didn't even notice the changes between 2.0 and 2.1).
Thanks to the first number, any radical change in the suite can still be
marked by passing from SM 2.* to 3.*, and in that case all extensions
would correctly require a new check (whereas firefox extensions have the
problem that they can never now whether a change in the first number
will mean a small or big change, and can thus never use a max version of
*, and will have to update their extension every single release).
--
Francesco
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
