Program Management/Programs/Silent Update/2011-12-01

Features

Removal of OS security dialog for Windows

Owner: Brian

QA (Simona Badau)

• Test Plan
• Completed:
  • created and ran test cases on the following platforms: Win XP 32-bit, 64-bit, Win 7 32-bit, 64-bit, Win Vista 32 bit, 64-bit, Win 2000 (http://bit.ly/v74fFt)
  • added test cases in Litmus
  • exploratory work on the builds from the elm branch
  • communicated issues found to Brian for feedback
• What's Next:
  • create and run more test cases
  • updates on the existing Test Plan
• Questions/Issues:
  • No unresolved questions or issues at this time

Add-ons Default to Compatible

Owner: Blair (client), Wil (AMO)

• Client
  • bug 693906 Parse and use new compatibility ranges in AMO metadata ping
    • patch ready for review
  • bug 527141 Addon update check should take into account compatibility preferences
    • patch ready for review
  • bug 705530 Support strictCompatibility option in update.rdf
    • ready to land
  • bug 706387 Send the compatibility mode when using AMO Search API
    • New
• AMO
  • bug 706385 Add compatMode param to Search API
    • targeted to be fixed this week
  • bug 703783 Update version check to assume strict compatibility when addon has binary components
    • targeted to be fixed this week
  • bug 703781 Update version check script to use compat overrides
    • targeted to be fixed this week

QA (Virgil Dicu)

• Test Plan
• Completed:
  • verified some fixed bugs
  • filed bug 706424 - Downgrading to Firefox<10 lists add-ons with minVersion higher than application version as compatible
  • Litmus testcases added here
  • started running weekly exploratory tests on the following platforms: Windows XP, Windows 7, Ubuntu, Mac OS
  • ran new test scenarios: behavior when downgrading, upgrading through more than two Firefox builds (7.0.1->8.0.1->9b3->10->11)
  • updated test plan to reflect changes and tests done recently
• What's Next
  • bug 695977 - Addons shouldn't be compatible by default when their minVersion is greater than the app version: need to test once enabled by default on Aurora
  • continue running a weekly exploratory across platforms
  • finish off adding test cases in-Litmus
  • run those tests on a weekly basis once they're added
• Questions/Issues
  • Is there anything I can do related to QA work for AMO side for this feature? (bug 691834)

Background updates

Owner: Ehsan

QA (Vlad Ghetiu)

• Test Plan
• Completed:
  • test plan and initial test cases created
• What's Next:
  • need to run test cases across multiple platforms
• Questions/Issues:
  • have been unable to get updates on the ASH channel -- is this closed?

Updated workflow for updating users with incompatible add-ons

Owner: Rob, Chris

QA (Ioana Budnar)

• Test Plan
• Completed
  • test plan created and revised as per meeting notes and discussions with Blair
• What's Next
  • continue to revise test plan as feature is implemented
• Questions/Issues
  • In case only x updated add-ons out of y incompatible ones (x<y) are found and the grace period ends, will the x add-ons be automatically updated when the user clicks "Update now"(after 7 days) or when the forced Firefox upgrade is done (after 14 days)?
  • When will the check for updated add-ons be performed, daily at some set time or when the user starts Fx? (e.g. If the user starts Firefox then leaves it open for 3 days, how many checks will be done?) Same for the check if the grace period has ended.
  • Will there be one process that first checks if the grace period has ended and if not, checks for updated add-ons? Or will the be separated (if separated, will it be possible the check forthe end of the grace period comes after the one for updated add-ons, when updated versions for all the add-ons are found?)
  • Will the user have a way of changing the grace period from 14 days to a number of days of his choice? If this won't be done for the end user, it would be good to have it at least for testing (otherwise we will have to wait for 1-2 weeks for some test cases to be done).