Re:Firefox update policy: the enterprise is wrong, not Mozilla
by potch on Monday June 27, 2011 @08:51PM
(#2703583)
Hello! I work for Mozilla. To address the problems with our extension versioning system, we've begun running an automated suite of tests against addons that will automatically make them as compatible with the next version of Firefox. The system performed well for the 4 -> 5 update, and we expect to tune it better. Additionally, if developers use the new set of extension APIs as opposed to the older ones, compatibility is a much simpler affair.
Re:Firefox update policy: the enterprise is wrong, not Mozilla
by cbf on Monday June 27, 2011 @09:57PM
(#2703726)
Is it safe to assume that every release is going to require binary XPCOM components to be rebuilt?
Re:Firefox update policy: the enterprise is wrong, not Mozilla
by joedrew on Monday June 27, 2011 @10:55PM
(#2703845)
Yes. We make no guarantees whatsoever on binary compatibility between versions.
Re:Firefox update policy: the enterprise is wrong, not Mozilla
by cbf on Monday June 27, 2011 @11:27PM
(#2703938)
Okay, thanks - has bundling an NPAPI plugin with an extension got a future? (js-ctypes can't do what I want so it seems like the next best thing.)
Re:Firefox update policy: the enterprise is wrong, not Mozilla
by dochtman on Tuesday June 28, 2011 @03:56AM
(#2704503)
Curious what you want to do... Maybe extend js-ctypes so that it'll do what you want?
Re:Firefox update policy: the enterprise is wrong, not Mozilla
by cbf on Tuesday June 28, 2011 @06:28AM
(#2704827)
I use an API that you pass a callback into and get an fd in response. You then monitor the fd and invoke a process function when there's something to read which results in your callback being fired with results. I haven't checked js-ctypes for some time so I could be wrong about this type of thing not being possible with it.
I figure if I'm going to do a rewrite I might as well go down the NPAPI path (via http://www.firebreath.org/) as then I can pick up Chrome.
Do they expect all developers to release a new version of their extensions every 6 weeks, or do they expect us to effectively say "my extension is compatible with every future version of firefox" which is impossible to guarantee?
There are very good reasons for the "major" version number to exist. Why would they ditch that? Just bump a minor number instead... I see no benefit to this approach.