Last Comment Bug 706796 - Addons that haven't been updated for an extremely long time should not be compatible by default
: Addons that haven't been updated for an extremely long time should not be com...
Product: Thunderbird
Classification: Client Software
Component: General (show other bugs)
: Trunk
: All All
-- normal (vote)
: Thunderbird 11.0
Assigned To: Mark Banner (:standard8)
Depends on: 700201
  Show dependency treegraph
Reported: 2011-12-01 04:52 PST by Mark Banner (:standard8)
Modified: 2011-12-07 02:12 PST (History)
0 users
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---

The fix (779 bytes, patch)
2011-12-01 08:02 PST, Mark Banner (:standard8)
bwinton: review+
standard8: approval‑comm‑aurora+
Details | Diff | Splinter Review

Description User image Mark Banner (:standard8) 2011-12-01 04:52:41 PST
+++ This bug was initially created as a clone of Bug #700201 +++

Just like Firefox have done in bug 700201 we should provide a default minimum version that add-ons older than that won't be compatible for.

Firefox have put this at FF 4 / Gecko 2. I'm proposing we do TB 5 (and still gecko 2). This was the release after 3.1 and had all the extension manager rework, and component registration changes that FF 4 had. Therefore I think it is a sensible baseline.

We'll want this on both trunk & aurora as both of those have the possibility to turn off strict checking.
Comment 1 User image Mark Banner (:standard8) 2011-12-01 08:02:02 PST
Created attachment 578267 [details] [diff] [review]
The fix

Adds the required pref for the min compatible version.
Comment 2 User image Blake Winton (:bwinton) (:☕️) 2011-12-01 08:16:30 PST
Comment on attachment 578267 [details] [diff] [review]
The fix

Review of attachment 578267 [details] [diff] [review]:

Of course, I'ld prefer us to use 1.0, but I guess this'll do.  ;)
Comment 3 User image Mark Banner (:standard8) 2011-12-01 11:47:52 PST
Checked in:
Comment 4 User image Mark Banner (:standard8) 2011-12-07 02:12:29 PST
Landed on aurora:

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