Comment: Re:Finally (Score 3, Interesting) 411
As someone with a very basic understanding of plugins (we have a custom toolbar we roll out with internal apps and links) I can tell you it is an issue. As an add-on developer you have to build into the toolbar "this add-on is good for FF versions x through y" that is in an xml file required for the toolbar to run. So you as a developer have 2 options you can say that your toolbar will work with version 1 through 999999 and just hope that a firefox update really doesn't ever break your add-on OR you can update it with every release ensuring that it works with the new version and require your users / (admins in corp environment) to update the add-on every time. Both of the above options have there drawbacks.
My major issue with the firefox team is that they changed the rules in the middle of the game. It used to be that if I put this add-on will work with this new version it would be good for about a year. Now I need to add in 6 weeks per version so if i want it to be good for a year I divide 52 weeks by 6 week major upgrade cycle and add 8.6~9 to the version number for it to work for about a year. All of this is assuming Mozilla doesn't change there major release version system again. If they decide to go back to the old way then my add-on will last for 9 years and will almost certainly be broken by a release at some point along the way.