Last Comment Bug 731779 - Integrate the Add-on SDK loader and API libraries into Firefox
: Integrate the Add-on SDK loader and API libraries into Firefox
Status: ASSIGNED
[leave open]
:
Product: Firefox
Classification: Client Software
Component: General (show other bugs)
: unspecified
: All All
: P1 normal with 5 votes (vote)
: ---
Assigned To: Irakli Gozalishvili [:irakli] [:gozala] [@gozala]
:
:
Mentors:
https://wiki.mozilla.org/Add-on_SDK_i...
: 659104 (view as bug list)
Depends on: 719206 731803 756542 787346 793912 793916 793924 793925 793926 793928 793932 793934 820688 821025 826933
Blocks: 837434 673391
  Show dependency treegraph
 
Reported: 2012-02-29 14:00 PST by Dietrich Ayala (:dietrich)
Modified: 2014-04-02 18:05 PDT (History)
28 users (show)
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---
21+


Attachments

Description Dietrich Ayala (:dietrich) 2012-02-29 14:00:07 PST
Meta-bug.
Comment 1 John Nagle 2012-03-06 22:38:46 PST
In conjunction with this, I'd suggest handling compatibility checking as follows: 

1. The add-on API should have two version numbers. The upper version number increases when a new feature is added to the API. The lower version number increases only when an old feature is removed or changed incompatibly. (Based on the documentation, that hasn't happened in the last year.) These numbers are independent of the Firefox version.

2. Add-ons have one API version number.

3. An add-on is compatible if its version number is within the upper and lower API version numbers.

This gives add-ons much longer lives, and eliminates much of the current fussing over version issues. Only deletion of an API feature should invalidate an add-on.  A major point of the Jetpack API was to have a reasonably stable API to work against. This has been achieved, but there's still too much frantic updating required, and too many add-ons dying off.
Comment 2 Henrik Skupin (:whimboo) [away 09/30 - 10/06] 2012-03-07 03:32:52 PST
One good example of it would be the ESR releases. As for now (as what I have heard) we do not support them. It means with SDK 1.6 the minVersion will be bumped to 11.0 even with probably no older API getting removed.
Comment 3 Jeff Griffiths (:canuckistani) (:⚡︎) 2012-08-29 05:50:54 PDT
This bug is now being treated as the top-level bug for tracking the landing and shipping of the Add-on SDK's loader and apis in Firefox. If work is being done to further this effort, it should block this bug.
Comment 4 Wes Kocher (:KWierso) 2012-08-31 02:13:47 PDT
*** Bug 659104 has been marked as a duplicate of this bug. ***
Comment 6 Phil Ringnalda (:philor) 2013-02-03 12:46:17 PST
https://hg.mozilla.org/mozilla-central/rev/a874d2756f65

Note You need to log in before you can comment on or make changes to this bug.