Closed
Bug 729557
Opened 12 years ago
Closed 12 years ago
Need Firefox icon for MWC specified Nightly build
Categories
(Firefox for Android Graveyard :: General, defect, P1)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jfu, Assigned: elan)
References
(Blocks 1 open bug)
Details
To keep our brand consistent, we will need the Nightly build we're using at MWC to have a Firefox logo instead of the Nightly logo. Erin - can you provide info on which build we're going with? Thanks!
(referring to the app icon you see on your Android home screen)
Updated•12 years ago
|
Assignee: nobody → elancaster
Comment 3•12 years ago
|
||
This means we'll need to do a special one-off build with official branding. Personally, I would not want to do that. We only use official branding for official release builds. This would not be an official release build.
Comment 4•12 years ago
|
||
I would agree. That feels wrong to me as well.
Assignee | ||
Comment 5•12 years ago
|
||
OK, let me check with Chris Beard.
Comment 6•12 years ago
|
||
This will be for the builds installed on the demo devices only. It will not be for distribution. I want to use the Firefox logo for these as we don't want to introduce new brands or complexity, and people picking up the devices to "play around" should only have to think "let me check out Firefox" vs. "I wonder what this globe icon is?" I hope that clears it up. I don't know if there is an easy way to do this, but it's something we should try to do for MWC only.
This makes sense to me; fall back is currently the 2/19 build; we will be testing the 2/23 build with the latest web api tonight (waverly) and tomorrow. There are some checkins to make the Awesome Page faster today.
Updated•12 years ago
|
Flags: blocking-fennec1.0+
Comment 8•12 years ago
|
||
Damon - Does this bug block release? I don't think it does, but even so, I don't think we are using the blocking-fennec1.0 flag anymore. Use the fennecnative-beta(release)blocker keyword.
Not sure if we have enough time for releng to complete this and QA to qualify. CC'ing aki and joduinn.
Comment 10•12 years ago
|
||
I think we can get this by pushing whatever changeset we want to Try, with official branding instead of nightly branding.
Updated•12 years ago
|
OS: Mac OS X → Android
Hardware: x86 → ARM
Comment 11•12 years ago
|
||
https://hg.mozilla.org/try/rev/6c01e697fafd https://tbpl.mozilla.org/?tree=Try&rev=6c01e697fafd Builds will show up here: http://ftp.mozilla.org/pub/mozilla.org/firefox/try-builds/asasaki@mozilla.com-6c01e697fafd
Comment 12•12 years ago
|
||
Per Naoki, we want to have a branded build off the same revision as the 2/23 m-c android native nightly. Per http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/2012-02-23-03-12-36-mozilla-central-android/fennec-13.0a1.en-US.android-arm.txt , that's http://hg.mozilla.org/mozilla-central/rev/5e756e59a794 . I submitted the following build to try: Thanks for your try submission (http://hg.mozilla.org/try/pushloghtml?changeset=613c55c76ead). It's the best! Watch https://tbpl.mozilla.org/?tree=Try&rev=613c55c76ead for your results to come in. Builds and logs will be available at http://ftp.mozilla.org/pub/mozilla.org/firefox/try-builds/asasaki@mozilla.com-613c55c76ead.
OS: Android → Mac OS X
Hardware: ARM → x86
Updated•12 years ago
|
OS: Mac OS X → Android
Hardware: x86 → ARM
Comment 13•12 years ago
|
||
We did these builds for MWC.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•3 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•