Firefox3.5/AddonsCompatibility: Difference between revisions
Jump to navigation
Jump to search
(→Tasks) |
ChrisHofmann (talk | contribs) No edit summary |
||
| Line 4: | Line 4: | ||
= Tasks = | = Tasks = | ||
== Preparation == | |||
* Get addons developer blog up and running | * Get addons developer blog up and running | ||
* Get docs lined up to help addon developers make the transition | |||
** http://developer.mozilla.org/en/Firefox_3.1_for_developers#For_XUL_and_application_developers | |||
* Revive the addons compatibility dashboard | |||
** Something like http://people.mozilla.com/~polvi/threedom/status-bars.html to track full list of addons sorted by usage popularity and identify current compat version. get it to update every night. | |||
* Set up tracking bugs for the top 50-60 addons to track progress on contacting, updating, and feedback about how things are going with getting compatible. ala https://bugzilla.mozilla.org/showdependencytree.cgi?id=364745&hide_resolved=0 | |||
* Figure out plan for scaling review queue if/when it gets flooded in Nov/Dec/Jan | |||
== Outreach == | |||
* Send out emails to developers and editors | * Send out emails to developers and editors | ||
* Post to blog and newsgroup detailed information about what is changing and how to update | * Post to blog and newsgroup detailed information about what is changing and how to update | ||
* | * Out reach to press or on-line awareness like http://lifehacker.com/393559/firefox-3-add+on-compatibility-report | ||
= Schedule = | = Schedule = | ||
Revision as of 18:59, 16 October 2008
Goals
- Increase awareness about addons API changes in Firefox 3.1
- Assist developers with the update process
Tasks
Preparation
- Get addons developer blog up and running
- Get docs lined up to help addon developers make the transition
- Revive the addons compatibility dashboard
- Something like http://people.mozilla.com/~polvi/threedom/status-bars.html to track full list of addons sorted by usage popularity and identify current compat version. get it to update every night.
- Set up tracking bugs for the top 50-60 addons to track progress on contacting, updating, and feedback about how things are going with getting compatible. ala https://bugzilla.mozilla.org/showdependencytree.cgi?id=364745&hide_resolved=0
- Figure out plan for scaling review queue if/when it gets flooded in Nov/Dec/Jan
Outreach
- Send out emails to developers and editors
- Post to blog and newsgroup detailed information about what is changing and how to update
- Out reach to press or on-line awareness like http://lifehacker.com/393559/firefox-3-add+on-compatibility-report
Schedule
- Milestone 1 - Oct 24
- Milestone 2 - Nov 7
- Milestone 3 - Nov 21