Closed
Bug 811244
Opened 12 years ago
Closed 12 years ago
Check for system updates after conclusion of FTE
Categories
(Firefox OS Graveyard :: Gaia::System, defect, P1)
Tracking
(blocking-basecamp:+)
People
(Reporter: jcarpenter, Assigned: etienne)
References
Details
(Keywords: feature)
Attachments
(1 file)
2.16 KB,
patch
|
vingtetun
:
review+
|
Details | Diff | Splinter Review |
It is likely that a system update will be available to v1 phone customers on launch day. We want to push that update aggressively. If users are connected to the web, we should automatically poll for available system updates soon after their FTE experience has concluded. Not _immediately_ after (it would be obnoxious to experience an update prompt as your welcome to the FxOS experience), but within a short time span (say five minutes?) of completing the last step of the FTE Setup, regardless of whether the user opts to view the tour or not.
User story:
> As a user, once the FTE Setup and/or Tutorials conclude and I am
> connected to the internet connection, I want the system to automatically
> check for available system updates, so that I can keep for phone
> software up to date.
Blocking+ because of importance of pushing this update to end users.
Reporter | ||
Updated•12 years ago
|
Component: Gaia → Gaia::System
Assignee | ||
Comment 1•12 years ago
|
||
Probably just a matter of doing the magical mozSetting update like the force-check button in the Settings app does.
Comment 2•12 years ago
|
||
+1 on this. We'll have months of security/usability fixes under our belt at launch, so this is a security/quality concern and should be b-b+. The only reason I'm not plusing already is that I'd like triage to find an assignee.
Hoping we can get this done in the C1 timeframe, since this is remaining feature work.
Priority: -- → P1
Target Milestone: --- → B2G C1 (to 19nov)
Updated•12 years ago
|
Flags: needinfo?(jcarpenter)
Don't we already have a delay timer for checking for updates? app.update.timerMinimumDelay;120, app.update.interval;28800
Do we need a firstrun bug? Also Would it make more sense to have a last page asking if they want to check for updates in the FTE?
Flags: needinfo?(jcarpenter)
Don't we already have a delay timer for checking for updates? app.update.timerMinimumDelay;120, app.update.interval;28800
Do we need a firstrun bug? Also Would it make more sense to have a last page asking if they want to check for updates in the FTE?
Updated•12 years ago
|
Assignee: nobody → fbsc
Reporter | ||
Updated•12 years ago
|
Flags: needinfo?(jcarpenter)
Updated•12 years ago
|
Assignee: fbsc → nobody
Comment 7•12 years ago
|
||
Checking 'Updates' it's not part of FTE App... Do you who was in charge of updates?
Comment 8•12 years ago
|
||
*Do you know who was in charge of 'updates'?
Comment 9•12 years ago
|
||
Correct, it's not really part of FTE, but the first update check should be triggered at the conclusion of FTE, so it seems like that's the app that needs the change.
Etienne, are you a better choice to take this one?
Assignee: nobody → etienne
Updated•12 years ago
|
Summary: [FTE] Check for system updates after conclusion of FTE → Check for system updates after conclusion of FTE
Comment 10•12 years ago
|
||
I've modified the name due to it's not part of FTE. Thanks!
Assignee | ||
Comment 11•12 years ago
|
||
(In reply to Dylan Oliver [:doliver] from comment #9)
> Correct, it's not really part of FTE, but the first update check should be
> triggered at the conclusion of FTE, so it seems like that's the app that
> needs the change.
>
> Etienne, are you a better choice to take this one?
np
Assignee | ||
Comment 12•12 years ago
|
||
Attachment #683207 -
Flags: review?(21)
Attachment #683207 -
Flags: review?(21) → review+
Assignee | ||
Comment 13•12 years ago
|
||
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•