Created attachment 688104 [details] [diff] [review] Patch We missed a spot... Without this, our 3G will fail. This is absolutely my bad. Feel really guilty and sorry about that.
Attachment #688104 - Flags: review?(vyang)
Attachment #688104 - Flags: review?(vyang) → review+
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla20
This bug relates to MMS features and needs to be tagged as leo+ so that we can uplift it into the b2g-18 branch.
blocking-b2g: --- → leo?
status-b2g18: --- → fixed
status-b2g18-v1.0.0: --- → wontfix
status-b2g18-v1.0.1: --- → wontfix
status-firefox20: --- → fixed
requesting uplift to 1.0.1 per bug 846230
blocking-b2g: leo+ → tef+
status-b2g18-v1.0.1: wontfix → affected
status-b2g18-v1.0.1: affected → fixed
This is causing 3G and WiFi to fail (see bug 856997), can we back this out and look for a an alternative solution for bug 846230 that does not require to uplift this bug (that is intended for 1.1)
Backed out for now. The release drivers and developers will need to decide the proper way to proceed with this for v1.0.1. https://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/512258bc00a3
status-b2g18-v1.0.1: fixed → affected
This bug is aimed for a follow-up fix for bug 777251. I don't really believe it can be checked in independently...
(In reply to Gene Lian [:gene] from comment #10) > This bug is aimed for a follow-up fix for bug 777251. I don't really believe > it can be checked in independently... Then we should mark this as depending on bug 777251, right?
(In reply to Daniel Coloma:dcoloma from comment #11) > (In reply to Gene Lian [:gene] from comment #10) > > This bug is aimed for a follow-up fix for bug 777251. I don't really believe > > it can be checked in independently... > > Then we should mark this as depending on bug 777251, right? For the follow-up bug, we usually use blocking instead of depending. And I don't think it's worth uplifting the bug 777251 since it must touch lots of related MMS bugs which need to be uplifted due to the code conflict, too. Per comment #8, it'd be better to find out an branch-specific alternative to get through it.
You need to log in before you can comment on or make changes to this bug.