Program Management/Programs/Silent Update/2011-11-17: Difference between revisions

no edit summary
No edit summary
 
(One intermediate revision by one other user not shown)
Line 61: Line 61:
==New workflow for updating users with incompatible add-ons==
==New workflow for updating users with incompatible add-ons==
Owner: Rob, Chris
Owner: Rob, Chris
* Chris was to follow up with Alex Limi last week about the new button.
* Chris met with Limi and updated the wiki page with revised specs
* Limi will follow-up with UX specs shortly
* Once we move to add-ons default to compatible, the majority of incompatible add-ons will be ones with binary components
* Add-ons which are incompatible and the user decides to move forward with the update, we will only disable
* "not now" should suppress the dialog for X days, and not til the next Firefox update


; QA (Ioana Budnar)
; QA (Ioana Budnar)
Line 68: Line 72:
* To Do:
* To Do:
** Continue to revise test plan as feature develops
** Continue to revise test plan as feature develops
* Questions:
* Questions (answers above):
** Are the binary add-ons the only ones that should be listed in the prompt about unsupported add-ons?
** 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?
** 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?
Line 78: Line 82:
; QA (ashughes)
; QA (ashughes)
* How has the interaction been compared to recent weeks?
* How has the interaction been compared to recent weeks?
** Consensus is that the dev/QA interaction has definitely improved.
canmove, Confirmed users, Bureaucrats and Sysops emeriti
496

edits