I'm not quite sure why the following change didn't make it to the files in hg.mozilla.org/gaia-l10n/en-US when we were string-freezing on September 28. https://github.com/mozilla-b2g/gaia/commit/12a75b0821e6bf52a9a4de621a4b679101b99992#L4L97 As a result, the localizers translated the old version of the string. To notify them of the change, we need to change the identifier. I'll have a patch in a moment to fix this.
Requesting blocking-basecamp. We can't provide good localizations without this fix.
blocking-basecamp: --- → ?
Milestoning for C2 (deadline of 12/10), as this meets the criteria of "remaining P1 bugs not already milestoned for C1".
Target Milestone: --- → B2G C2 (20nov-10dec)
Stas brought to our attention that this is actually late-l10n work. Bumping up to C1 (to be completed by Nov19) given that.
Target Milestone: B2G C2 (20nov-10dec) → B2G C1 (to 19nov)
Comment on attachment 674901 [details] [diff] [review] Patch Stas can you make a PR against the master branch?
Attachment #674901 - Flags: review+
Created attachment 682722 [details] Pointer to Github pull request: https://github.com/mozilla-b2g/gaia/pull/6472 Pointer to Github pull-request
Comment on attachment 682722 [details] Pointer to Github pull request: https://github.com/mozilla-b2g/gaia/pull/6472 NOTE: If blocking-basecamp+ is set, just land it for now. [Approval Request Comment] Bug caused by (feature/regressing bug #): User impact if declined: Testing completed: Risk to taking this patch (and alternatives if risky):
Comment on attachment 682722 [details] Pointer to Github pull request: https://github.com/mozilla-b2g/gaia/pull/6472 Blocking+, no need for approval.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.