[Flame L] add flame-l.xml for v2.2

RESOLVED FIXED in FxOS-S1 (26Jun)

Status

defect
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: viralwang, Assigned: viralwang)

Tracking

unspecified
FxOS-S1 (26Jun)
ARM
Gonk (Firefox OS)
Dependency tree / graph

Firefox Tracking Flags

(blocking-b2g:2.2+, b2g-v2.2 fixed, b2g-master fixed)

Details

Attachments

(1 attachment)

as bug 1174670 discussion, we should have flame-l.xml for v2.2
then we can have v2.2 PVT build
Hi Michael,

I would like to add flame-l.xml in v2.2 branch.
Could you please help to review it?
Thank you.
Attachment #8626081 - Flags: review?(mwu)
Branch backports require blocking/approval, not reviews.
Attachment #8626081 - Flags: review?(mwu)
blocking-b2g: --- → 2.2+
Blocks: Flame_L
Comment on attachment 8626081 [details] [review]
PR for flame-l.xml in v2.2

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 #): NA
User impact if declined: we need this xml for flame-l with branch v2.2
Testing completed: yes, I did the local testing
Risk to taking this patch (and alternatives if risky): low, it only used for v2.2 and flame-l.
String or UUID changes made by this patch: NA
Attachment #8626081 - Flags: approval-mozilla-b2g37?
Comment on attachment 8626081 [details] [review]
PR for flame-l.xml in v2.2

Approving as this is required for Flame-L build
Attachment #8626081 - Flags: approval-mozilla-b2g37? → approval-mozilla-b2g37+
v2.2: https://github.com/mozilla-b2g/b2g-manifest/commit/b4c1ea5d3bb1db697afd4c08256b743008af8c75
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → FxOS-S1 (26Jun)
You need to log in before you can comment on or make changes to this bug.