Closed
Bug 868391
Opened 12 years ago
Closed 12 years ago
[Building Blocks] Alerts should be updated to the latest version
Categories
(Firefox OS Graveyard :: Gaia, defect)
Tracking
(b2g18 fixed)
RESOLVED
FIXED
| Tracking | Status | |
|---|---|---|
| b2g18 | --- | fixed |
People
(Reporter: sergiov, Assigned: arnau)
Details
Attachments
(2 files)
|
37.21 KB,
image/png
|
Details | |
|
273 bytes,
text/html
|
basiclines
:
review+
lsblakk
:
approval-gaia-v1+
|
Details |
Alerts have been updated in the Common Controls file: https://www.dropbox.com/s/xaohxz39nh9ft7u/CommonControls_20130305.jpg
we should update the building block to match this update.
| Assignee | ||
Comment 1•12 years ago
|
||
Attachment #745114 -
Flags: review?(igonzaleznicolas)
Comment 2•12 years ago
|
||
Comment on attachment 745114 [details]
patch to github
Everything looks good
Attachment #745114 -
Flags: review?(igonzaleznicolas) → review+
| Assignee | ||
Comment 3•12 years ago
|
||
Comment on attachment 745114 [details]
patch to github
NOTE: Please see https://wiki.mozilla.org/Release_Management/B2G_Landing to better understand the B2G approval process and landings.
[Approval Request Comment]
Bug caused by (feature/regressing bug #):
User impact if declined: not matching visual style
Testing completed: yes
Risk to taking this patch (and alternatives if risky): very low, just CSS
String or UUID changes made by this patch:
Attachment #745114 -
Flags: approval-gaia-v1?
| Assignee | ||
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Attachment #745114 -
Flags: approval-gaia-v1? → approval-gaia-v1+
Updated•12 years ago
|
status-b2g18-v1.0.1:
--- → affected
Comment 4•12 years ago
|
||
I was not able to uplift this bug to v1-train. If this bug has dependencies which are not marked in this bug, please comment on this bug. If this bug depends on patches that aren't approved for v1-train, we need to re-evaluate the approval. Otherwise, if this is just a merge conflict, you might be able to resolve it with:
git checkout v1-train
git cherry-pick -x -m1 8513e27db3232a71a2e3eec90c8985930cd48540
<RESOLVE MERGE CONFLICTS>
git commit
Comment 5•12 years ago
|
||
Arnau or Isma, could you help John with th uplift to v1-train?
Flags: needinfo?(igonzaleznicolas)
Flags: needinfo?(arnau)
| Assignee | ||
Updated•12 years ago
|
| Assignee | ||
Comment 6•12 years ago
|
||
v1-train: ba61586cdb80791369e07be4e609e6369f04621c
Flags: needinfo?(igonzaleznicolas)
Flags: needinfo?(arnau)
Comment 7•12 years ago
|
||
Thanks for the resolution. V1-train is currently v1.1.0, and we're using the status-b2g18 flag for that.
fixing flag
status-b2g18:
--- → fixed
status-b2g18-v1.0.1:
fixed → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•