Firefox/Features/Easier Add-on Compatibility: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
(→Plan) |
||
| Line 23: | Line 23: | ||
The details of this plan are located [http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/99e372313db48cda# here]. They will be cleaned up and moved to this wiki in April. | The details of this plan are located [http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/99e372313db48cda# here]. They will be cleaned up and moved to this wiki in April. | ||
Bugs for tools implementation are [https://bugzilla.mozilla.org/buglist.cgi?status_whiteboard_type=allwordssubstr&status_whiteboard= | Bugs for tools implementation are [https://bugzilla.mozilla.org/buglist.cgi?status_whiteboard_type=allwordssubstr&status_whiteboard=conveyorbelt&product=addons.mozilla.org here]. | ||
__NOTOC__ | __NOTOC__ | ||
Latest revision as of 22:49, 18 April 2011
| Feature | Status | ETA | Owner |
| Solution to frequent compatibility updates | Tools implementation underway. | 2011-06-01 | Justin Scott |
Summary
The manual, multi-month add-on compatibility process that has been used in previous releases of Firefox is not feasible for quarterly releases.
Add-ons that don’t use binary components should not require manual compatibility updates with new Firefox releases unless directly affected by a compatibility change. Such breaking compatibility changes should be minimal and well-documented.
Plan
The details of this plan are located here. They will be cleaned up and moved to this wiki in April.
Bugs for tools implementation are here.