Confirmed users
2,473
edits
Features/Add-ons/Add-ons Default to Compatible: Difference between revisions
Features/Add-ons/Add-ons Default to Compatible (view source)
Revision as of 21:23, 9 November 2011
, 9 November 2011no edit summary
No edit summary |
No edit summary |
||
| Line 52: | Line 52: | ||
|Feature implementation notes=* Add-ons Manager bug: {{bug|692664}} ([https://bugzilla.mozilla.org/showdependencytree.cgi?id=692664 Dependency tree]) | |Feature implementation notes=* Add-ons Manager bug: {{bug|692664}} ([https://bugzilla.mozilla.org/showdependencytree.cgi?id=692664 Dependency tree]) | ||
* In order to land in 10 requires | * In order to land in 10 requires | ||
** {{bug|698653}} Flip extensions.strictCompatibility pref in Firefox to | ** {{bug|698653}} Flip extensions.strictCompatibility pref in Firefox to make addons compatible-by-default (one-line patch to turn the feature on) | ||
make addons compatible-by-default (one-line patch to turn the feature on) | ** {{bug|695977}} Addons shouldn't be compatible by default when their minVersion is greater than the app version (I think the patch is done, but I've been holding off because half the logic is in the patch for {{bug|527141}}, which is unfinished and I need to make sure I haven't missed anything) | ||
** {{bug|695977}} Addons shouldn't be compatible by default when their | ** {{bug|700201}} Addons that haven't been updated for an extremely long time should not be compatible by default (only recently filed, haven't started work on it yet, but it's pretty simple) | ||
minVersion is greater than the app version (I think the patch is done, | |||
but I've been holding off because half the logic is in the patch for bug | |||
527141, which is unfinished and I need to make sure I haven't missed | |||
anything) | |||
** {{bug|700201}} Addons that haven't been updated for an extremely long | |||
time should not be compatible by default (only recently filed, haven't | |||
started work on it yet, but it's pretty simple) | |||
* Preferable to also have | * Preferable to also have | ||
** {{bug|693906}} Parse and use new compatibility ranges in AMO metadata | ** {{bug|693906}} Parse and use new compatibility ranges in AMO metadata ping (Still working on this, patch needs a bunch more work and some additional tests. AMO side is done, with some followup bugs found by QA) | ||
ping (Still working on this, patch needs a bunch more work and some | ** {{bug|527141}} Addon update check should take into account compatibility preferences. Patch ready. Depends on AMO {{bug|698355}} | ||
additional tests. AMO side is done, with some followup bugs found by QA) | |||
** {{bug|527141}} Addon update check should take into account compatibility | |||
preferences. Patch ready. Depends on AMO {{bug|698355}} | |||
* Nice to have | * Nice to have | ||
** {{bug|570033}} Consider exposing add-on compatibility checking status of | ** {{bug|570033}} Consider exposing add-on compatibility checking status of the browser. | ||
the browser. | |||
* AMO bug: {{bug|691834}} ([https://bugzilla.mozilla.org/showdependencytree.cgi?id=691834 Dependency tree]) | * AMO bug: {{bug|691834}} ([https://bugzilla.mozilla.org/showdependencytree.cgi?id=691834 Dependency tree]) | ||
* In order to land in 10 requires | * In order to land in 10 requires | ||
** {{bug|698355}} in order to update addons that are compatible-by-default | ** {{bug|698355}} in order to update addons that are compatible-by-default | ||
** {{bug|698358}} in order to update the small | ** {{bug|698358}} in order to update the small sub-section of addons that opt-in to strict compatibility (none now, hopepfully very few in the future, but something we need to fully support) | ||
sub-section of addons that opt-in to strict compatibility (none now, hopepfully very few in the future, but something we need to fully support) | |||
}} | }} | ||
{{FeatureInfo | {{FeatureInfo | ||