Closed Bug 716760 Opened 8 years ago Closed 8 years ago

"Pair device" string addition

Categories

(Firefox for Android :: Android Sync, defect)

ARM
Android
defect
Not set

Tracking

()

RESOLVED FIXED
mozilla12
Tracking Status
firefox11 --- fixed

People

(Reporter: rnewman, Assigned: rnewman)

References

Details

(Keywords: late-l10n)

Attachments

(1 file)

I'd like to get a small change landed now, so we can get it neatly into Aurora and into the hands of localizers.
Feel free to throw this at someone else if I picked the wrong reviewer!
Assignee: nobody → rnewman
Status: NEW → ASSIGNED
Attachment #587223 - Flags: review?(blassey.bugs)
Attachment #587223 - Flags: review?(blassey.bugs) → review+
Thanks blassey!

Will flag for Aurora approval once this hits a green m-c.

https://hg.mozilla.org/integration/mozilla-inbound/rev/01d69766026d
Whiteboard: [inbound]
https://hg.mozilla.org/mozilla-central/rev/01d69766026d
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Whiteboard: [inbound]
Target Milestone: --- → mozilla12
Comment on attachment 587223 [details] [diff] [review]
Proposed patch. v1

[Approval Request Comment]
Regression caused by (bug #):
* No regression; new Java-only mobile strings.

User impact if declined:
* Delayed l10n time. This has to land *eventually*, so trying for sooner rather than later. No user impact yet.

Testing completed (on m-c, etc.):
* Builds. (Android builds fail if strings aren't a-ok.)

Risk to taking this patch (and alternatives if risky):
* Negligible.
Attachment #587223 - Flags: approval-mozilla-aurora?
Comment on attachment 587223 [details] [diff] [review]
Proposed patch. v1

[Triage Comment]
Mobile string freeze is coming up, so approving for Aurora now that this has baked on m-c for a couple of days.
Attachment #587223 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
> Mobile string freeze is coming up, so approving for Aurora now that this has
> baked on m-c for a couple of days.

Thanks Alex.

Can't land this until the first Android Sync drop lands (Bug 709391). If that doesn't happen, I guess it'll go in the *second* Android Sync drop, which will implicitly include the first and this change.

In the holding area it goes! :D
Richard, is this out of hold? And if so, does this still need to land?
Keywords: late-l10n
(In reply to Axel Hecht [:Pike] from comment #7)
> Richard, is this out of hold? And if so, does this still need to land?

We got approval for Aurora last week, so I landed everything in one go. Thanks for the catch! (I guess I need to spend time putting together some Bugzilla queries for "things that need attention"...)
Blocks: 721271
Verified:

$ diff ~/moz/hg/mozilla-aurora/mobile/android/base/locales/en-US/sync_strings.dtd ~/moz/hg/mozilla-central/mobile/android/base/locales/en-US/sync_strings.dtd
20c20
< <!ENTITY sync.link.advancedsetup.label 'Advanced setup...'>
---
> <!ENTITY sync.link.advancedsetup.label 'Advanced setup…'>

which is Bug 721305.
Product: Mozilla Services → Android Background Services
Product: Android Background Services → Firefox for Android
You need to log in before you can comment on or make changes to this bug.