Program Management/Programs/Silent Update/2011-11-17: Difference between revisions
< Program Management | Programs | Silent Update
Jump to navigation
Jump to search
| Line 26: | Line 26: | ||
Owner: Rob, Chris | Owner: Rob, Chris | ||
* Chris was to follow up with Alex Limi last week about the new button. | * Chris was to follow up with Alex Limi last week about the new button. | ||
; QA (Ioana Budnar) | |||
* Complete: | |||
** [[Silent_Update_not_now_prompt/TestPlan|Test Plan]] drafted | |||
* To Do: | |||
** Continue to revise test plan as feature develops | |||
* Questions: | |||
** Are the binary add-ons the only ones that should be listed in the prompt about unsupported add-ons? | |||
** When the user chooses to continue with the update and ignore the incompatible add-ons, are those add-ons simply disabled, or are they removed from Firefox? | |||
** Does "not now" suppress the dialog until the next add-on update, next Firefox update, next day, or download the update in the background? | |||
=Getting the word out= | =Getting the word out= | ||
* Ehsan's blog post was published on [http://ehsanakhgari.org/blog/2011-11-11/updating-firefox-background his blog] and on [http://blog.mozilla.com/futurereleases/2011/11/12/updating-firefox-in-the-background/ The Future of Firefox Blog]. | * Ehsan's blog post was published on [http://ehsanakhgari.org/blog/2011-11-11/updating-firefox-background his blog] and on [http://blog.mozilla.com/futurereleases/2011/11/12/updating-firefox-in-the-background/ The Future of Firefox Blog]. | ||
=Other= | =Other= | ||
Revision as of 22:19, 16 November 2011
Features
Removal of OS security dialog for Windows
Owner: Brian
Add-ons Default to Compatible
Owner: Blair (client), Wil (AMO)
- 3 client bugs required to complete this feature in Firefox 10
- bug 695977 Addons shouldn't be compatible by default when their minVersion is greater than the app version
- Granted Aurora (10) approval
- Depends on bug 527141 and AMO bug 698355
- bug 700201 Addons that haven't been updated for an extremely long time should not be compatible by default
- Granted Aurora (10) approval
- Discussion started on dev.platform
- bug 698653 Flip extensions.strictCompatibility pref in Firefox to make addons compatible-by-default
- Can be enabled once the other two bugs are complete
- bug 695977 Addons shouldn't be compatible by default when their minVersion is greater than the app version
- 2 AMO bugs required to complete this feature in Firefox 10
- bug 698355 Add compatMode parameter to VersionCheck.php to allow updating to non-compatible addon versions
- bug 698358 Add support for new strictCompatibility option in install.rdf
Background updates
Owner: Ehsan
- Implementation complete, ready for testing
New workflow for updating users with incompatible add-ons
Owner: Rob, Chris
- Chris was to follow up with Alex Limi last week about the new button.
- QA (Ioana Budnar)
- Complete:
- Test Plan drafted
- To Do:
- Continue to revise test plan as feature develops
- Questions:
- Are the binary add-ons the only ones that should be listed in the prompt about unsupported add-ons?
- When the user chooses to continue with the update and ignore the incompatible add-ons, are those add-ons simply disabled, or are they removed from Firefox?
- Does "not now" suppress the dialog until the next add-on update, next Firefox update, next day, or download the update in the background?
Getting the word out
- Ehsan's blog post was published on his blog and on The Future of Firefox Blog.