Confirmed users
716
edits
Gaia/System/Updates: Difference between revisions
→Open questions
| Line 104: | Line 104: | ||
* How often should we check for Gecko update? | * How often should we check for Gecko update? | ||
** Every 18 weeks, according to CLee's etherpad outline... | ** Every 18 weeks, according to CLee's etherpad outline... | ||
*** (sicking) This sounds too rare given that we ship Gecko updates every 6 weeks which always contain security updates. Usually we count on security researchers being able to reverse engineer those updates and create exploits for older versions of Gecko. | |||
* Can we confirm that there will be a back-up instance of Gecko in event of failed updates? If so, what will sequence of it's application be? | * Can we confirm that there will be a back-up instance of Gecko in event of failed updates? If so, what will sequence of it's application be? | ||
* Does being on 3G/Edge affect when we check for Gecko updates? | * Does being on 3G/Edge affect when we check for Gecko updates? | ||
| Line 114: | Line 115: | ||
* Should we inform users about how big updates will be before downloading them? Do we have the ability to tell before doing the actual download? | * Should we inform users about how big updates will be before downloading them? Do we have the ability to tell before doing the actual download? | ||
* Do we require the user to plug in the phone if battery is below X %? | * Do we require the user to plug in the phone if battery is below X %? | ||
** (sicking) See answer for Gonk | |||
* What prompts do we present to user? | * What prompts do we present to user? | ||
* Do we have a rollback strategy for failed installs? Previous April discussion w/ cjones indicated no... | * Do we have a rollback strategy for failed installs? Previous April discussion w/ cjones indicated no... | ||
| Line 120: | Line 122: | ||
* How many device reboots are required in the process? | * How many device reboots are required in the process? | ||
* Do we provide link to changelog so user can review update details before installing? | * Do we provide link to changelog so user can review update details before installing? | ||
** (sicking) See answer for Gonk | |||
* How large are these updates? | * How large are these updates? | ||
* Do we check for available device storage before downloading? If insufficient, how do we mitigate? | * Do we check for available device storage before downloading? If insufficient, how do we mitigate? | ||
* If the user powers down the device while an update is silently downloading in background, can we resume download later on? | * If the user powers down the device while an update is silently downloading in background, can we resume download later on? | ||
** (sicking) See answer for Gonk | |||
* How much user agency do we provide over installs? Can they defer? For how long? What affordances do we make for out of date Gecko? | * How much user agency do we provide over installs? Can they defer? For how long? What affordances do we make for out of date Gecko? | ||
* How can the user review the currently-installed version? From Settings? | * How can the user review the currently-installed version? From Settings? | ||
= Gaia Updates = | = Gaia Updates = | ||