Gaia/System/Updates: Difference between revisions

Gaia/System/Updates (view source)

Revision as of 00:19, 16 August 2012

853 bytes added , 16 August 2012

→‎Overview

Joshcarpenter

816

edits

@@ Line 125: / Line 125: @@
 == Overview ==
-* See the B2G Gecko update meta bug here:
-* Gecko updates can happen more frequently than Kernel updates.  Based on input from carriers and OEMs, it likely updates at this layer will need to happen somewhere between the current Desktop 6-week train interval and ESR (every 42 weeks).
+* Gecko always be updated atomically w/ Gaia
-* The proposed requirement here is to offer regular updates every 18 weeks.  This frequency offers Mozilla and our partners the ability to update functionality on the device at a quicker pace than other competitor OS stacks (iOS and Android), but at the same time not overwhelm our Carrier partners who may not be used to updating software so frequently.
+* Frequency:
-* Other requirements here are to offer a back-up instance of Gecko to ensure we can failover when necessary (if we somehow shipped an updated Gecko version that resulted in a bug).
+** More frequently than Gonk (kernel) updates.
-* The updates at the Gecko level should happen silently where the user is not aware of when this is happening.
+** Based on input from carriers and OEMs, it is likely that updates will need to happen somewhere between the current Desktop (6 week) and Extended Support Release (42 week) intervals. The proposed requirement is to offer regular updates every 18 weeks. This frequency offers Mozilla and our partners the ability to update functionality on the device at a quicker pace than competitor OS stacks (iOS and Android), but at the same time not overwhelm our Carrier partners who may not be used to updating software so frequently.
-* The user will not be charged any carrier network fees for any Gecko update (as agreed upon by Telefonica) given they will be making these updates via a private APN.
+* User prompts:
-* The user should be able to go into Settings > About to determine the version of the software the are using in order to debug and/or get support for any issue they encounter.
+** ...
+* Backups:
+** Requirements is to offer a back-up instance of Gecko to ensure we can failover when necessary (if we somehow shipped an updated Gecko version that resulted in a bug).
+** Probably a [https://bugzilla.mozilla.org/show_bug.cgi?id=715816#c1 Phase 2] item.
+* Cost: The user will not be charged any carrier network fees for any Gecko update, as agreed upon by Telefonica, who will be making these updates via a private APN.
+* User can view currently version information from Settings > Device > Device Information.
+* Update process:
+** Download
+*** Files will be binary diff'd to minimize size.
+*** If the interrupts download (turns of Airplane mode, powers off device, etc) we can theoretically complete at later time.
+*** Necko has the ability to download ranges, but this also needs server support. We certainly could require such support though. (as per Jonas)
+** Install
+*** Time to apply will vary depending on size of update, internal disk speed, device hardware spec, etc
+*** Will require restarting process (aprox 10 seconds), but not rebooting the device. Reboot _may_ be required as fail safe if /system is somehow left in read-write after the updater is finished.
+*** Battery life: We can detect current battery level, but not drain rate (which varies with battery age). It will also be difficult to estimate the amount of power required to complete an install. Therefore we should build healthy margins into any "minimum required battery" thresholds.
 == Bugs ==