Program Management/Programs/Silent Update/2011-11-17: Difference between revisions
< Program Management | Programs | Silent Update
Jump to navigation
Jump to search
(→Other) |
No edit summary |
||
(4 intermediate revisions by 2 users not shown) | |||
Line 3: | Line 3: | ||
==Removal of OS security dialog for Windows== | ==Removal of OS security dialog for Windows== | ||
Owner: Brian | Owner: Brian | ||
* MAR file verification should be done this week | |||
** will get releng the details they need this week | |||
* Should only support WinXP and above | |||
* Testing issues found on Vista and 2000 | |||
* Patches still require further review and refinement, nothing major | |||
; QA (Simona Badau) | ; QA (Simona Badau) | ||
Line 43: | Line 48: | ||
Owner: Ehsan | Owner: Ehsan | ||
* Implementation complete, ready for testing | * Implementation complete, ready for testing | ||
* Working on merging with Brian's patches, things seem to be progressing smoothly | |||
; QA (Vlad Ghetiu) | ; QA (Vlad Ghetiu) | ||
Line 55: | 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 | * 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 62: | 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 72: | 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. |
Latest revision as of 22:11, 17 November 2011
Features
Removal of OS security dialog for Windows
Owner: Brian
- MAR file verification should be done this week
- will get releng the details they need this week
- Should only support WinXP and above
- Testing issues found on Vista and 2000
- Patches still require further review and refinement, nothing major
- QA (Simona Badau)
- Complete
- Test plan is drafted
- Have been testing and writing test cases, consulting with Brian
- To Do
- Continue to test and implement tests
- Questions
- n/a
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
- QA (Virgil Dicu)
- Complete
- Test Plan drafted
- BFT tests drafted and executed on Win XP, Win 7, OS X 10.6, Ubuntu 11.10 (signed off for Aurora)
- Feedback requested on bug 702920 and bug 702868
- To Do
- Draft and execute tests for recently implemented bugs
- Testday this Friday will include exploratory testing of this feature
- Migrate test cases into Litmus
- Questions
- n/a
Background updates
Owner: Ehsan
- Implementation complete, ready for testing
- Working on merging with Brian's patches, things seem to be progressing smoothly
- QA (Vlad Ghetiu)
- Complete
- Test plan is drafted
- Have been testing and writing test cases, consulting with Ehsan
- To Do
- Continue to test and implement tests
- Questions
- n/a
New workflow for updating users with incompatible add-ons
Owner: Rob, Chris
- 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)
- Complete:
- Test Plan drafted
- To Do:
- Continue to revise test plan as feature develops
- Questions (answers above):
- 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.
Other
- QA (ashughes)
- How has the interaction been compared to recent weeks?
- Consensus is that the dev/QA interaction has definitely improved.