Closed Bug 1216498 Opened 9 years ago Closed 9 years ago

Bump SettinsDB version in order to enable pin the web

Categories

(Firefox OS Graveyard :: Gaia::System, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:2.5+, firefox44 fixed)

RESOLVED FIXED
FxOS-S10 (30Oct)
blocking-b2g 2.5+
Tracking Status
firefox44 --- fixed

People

(Reporter: gwagner, Assigned: gwagner)

References

Details

(Whiteboard: [systemsfe])

Attachments

(1 file)

Attached patch settings.diff (deleted) — Splinter Review
No description provided.
Attachment #8676204 - Flags: review?(mhenretty)
blocking-b2g: --- → 2.5+
Whiteboard: [systemsfe]
Assignee: nobody → anygregor
Blocks: pin-the-web
Comment on attachment 8676204 [details] [diff] [review] settings.diff Review of attachment 8676204 [details] [diff] [review]: ----------------------------------------------------------------- r+ for the idea. let's get a qa run to make sure this doesn't break anything else for the upgrade path.
Attachment #8676204 - Flags: review?(mhenretty) → review+
We need to do some upgrade testing after this lands. This needs to happen before the next OTA goes out.
Keywords: qawanted
I forgot; inbound builds don't have mar files so we can't update from that build location. We would need to have new builds pushed with that change set that creates updates.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → FxOS-S10 (30Oct)
After OTA update New Homescreen and Pin the Web were enabled after previous build had them disabled. Environmental Variables: Device: Aries 2.5 BuildID: 20151021172125 Gaia: 32d827a70af90a05918f234e5b16b35d5d2a07e8 Gecko: 2d3fd51c4182c253a2f102655e8e9e466032853f Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd Version: 44.0a1 (2.5) Firmware Version: D5803_23.1.A.1.28_NCB.ftf User Agent: Mozilla/5.0 (Mobile; rv:44.0) Gecko/44.0 Firefox/44.0 Build that was OTA'd from that had New Homescreen and Pin the Web off: Environmental Variables: Device: Aries 2.5 BuildID: 20151015110122 Gaia: 40ae7c292a36156458c66712b4bd61ecbe69272a Gecko: e193b4da0a8c1025aa76a403c64663ff1cd41709 Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd Version: 44.0a1 (2.5) Firmware Version: D5803_23.1.A.1.28_NCB.ftf User Agent: Mozilla/5.0 (Mobile; rv:44.0) Gecko/44.0 Firefox/44.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Keywords: qawanted
Thanks for the test! We should also do some sanity check with this update. There might be some other settings that haven't been enabled by default.
Naoki, do you recommend a smoketest run or some other testing here?
Flags: needinfo?(nhirata.bugzilla)
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
This was already handled the day of the land (a gaia test run) and after the land on an actual build. A smoke test was done the day after. We're going to do a dogfood run on the 23rd build and will also be releasing that as an OTA if things pass.
Flags: needinfo?(nhirata.bugzilla)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: