Closed Bug 778336 Opened 12 years ago Closed 12 years ago

Ensure FOTA updates do not erase user data prior to Nightly testing

Categories

(Firefox OS Graveyard :: General, defect)

defect
Not set
normal

Tracking

(blocking-basecamp:+)

RESOLVED INVALID
blocking-basecamp +

People

(Reporter: akeybl, Assigned: marshall)

References

Details

(Keywords: feature, Whiteboard: [B2GTest:Blocker][WebAPI:P1][LOE:S])

Ensure FOTA updates do not erase user data on update. This work needs to happen prior to Nightly testing.
I think meant to comment here in bug 778332 comment 2 ...

Anyway, as that notes, the FOTA client doesn't care about user data or not; what gets touched is determined by the update package itself.  If the update package doesn't say to blow away the data, the client won't do it.

Note, there are some cases in which we might want to clear user data for nightly testing, for example if we have to make a non-backwards-compatible DB change before release and can't invest resources in upgrade code.

I guess we can leave this open to verify the update packages, but this isn't a separate work item for bug 778084.
blocking-basecamp: --- → ?
blocking-basecamp: ? → +
Assignee: nobody → bsmith
Whiteboard: [B2GTest:Blocker] → [B2GTest:Blocker][WebAPI:P1]
Keywords: feature
Whiteboard: [B2GTest:Blocker][WebAPI:P1] → [B2GTest:Blocker][WebAPI:P1][LOE:S]
Marshall, is there anything remaining to do here?
Assignee: bsmith → marshall
OTA updates already keep the user data partition around, but FOTA updates are a little different.

Our current FOTA implementation is based on Google's recovery updater, which reads in a script that performs the update. Since this script is the real "logic" of the FOTA update, I would argue that there isn't much we can do in Gecko.

Whoever ends up creating the FOTA update-script will need to make sure that anything in the /data partition is preserved in the script itself.

Marking as RESOLVED INVALID for that reason. Reopen if you disagree..
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
In other words, the update package that's built has to go out of its way to remove any user data.
You need to log in before you can comment on or make changes to this bug.