Created attachment 670389 [details] [diff] [review] patch Mozilla is re-branding the App Marketplace to "Firefox Marketplace". This patch changes the 3 strings and bumps entities.
Attachment #670389 - Flags: review?(wjohnston)
Attachment #670389 - Flags: review?(wjohnston) → review+
Comment on attachment 670389 [details] [diff] [review] patch [Approval Request Comment] Bug caused by (feature/regressing bug #): User impact if declined: Mozilla Marketplace was rebranded to Firefox Marketplace and we need to update the brnading in-product. Testing completed (on m-c, etc.): landed on inbound Risk to taking this patch (and alternatives if risky): low risk, strings only String or UUID changes made by this patch: yes
Attachment #670389 - Flags: approval-mozilla-aurora?
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 19
Comment on attachment 670389 [details] [diff] [review] patch [Triage Comment] This change has been correctly made with an entity bump, and is a requirement for the Marketplace. I'll communicate it to dev-l10n. Do we need this in FF17 as well Mark?
Attachment #670389 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
(In reply to Alex Keybl [:akeybl] from comment #4) > Do we need this in FF17 as well Mark? Nope. We are turning it off for Fx17.
status-firefox18: --- → fixed
status-firefox19: --- → fixed
Why did this land on aurora when bug 798538 said it's fine for 19?
Status: RESOLVED → VERIFIED
status-firefox18: fixed → verified
status-firefox19: fixed → verified
(In reply to Axel Hecht [:Pike] (back Oct 29) from comment #7) > Why did this land on aurora when bug 798538 said it's fine for 19? Unfortunately, many other people were not fine with it riding on Fx19. The Marketplace team is highly focused on using Firefox 18 for Android as the initial launch vehicle and Marketing pushed very hard to get the "Firefox Marketplace" re-branding landed. It was a compromise to avoid the potential for string changes in Beta and beyond.
You need to log in before you can comment on or make changes to this bug.