We need to add csb and sw to browser/locales/all-locales on mozilla-aurora. PS: to be clear to the localization team, this bug is handled by mozilla staff. Depending on how quickly we get the repo for csb in bug 668773, we can do this in one patch for both sw and csb (sw has a repo already)
I believe, bug 668773 has been completed so, nothing to do here (?)
That bug is still missing some info.
Created attachment 548764 [details] [diff] [review] add csb and sw For now, we still need to add locales to both the repository and to buildconfig. This patch is only intended to land on aurora, and to neither go to central, nor to go to beta.
Assignee: nobody → l10n
Status: NEW → ASSIGNED
Attachment #548764 - Flags: approval-mozilla-aurora?
how does the 3-char locale code play with our locale matching regex's? Has this been tested?
We already have son, nso, etc.
Attachment #548764 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Per discussion on the triage meeting, landed this as two patches: csb: http://hg.mozilla.org/releases/mozilla-aurora/rev/c07180438c0c sw: http://hg.mozilla.org/releases/mozilla-aurora/rev/bcd02d1735e4
Status: ASSIGNED → RESOLVED
Last Resolved: 7 years ago
status-firefox7: --- → fixed
Resolution: --- → FIXED
What exactly should I do to verify this? Can anyone help?
Look for 8.0a2 builds in http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-aurora-l10n/ (Can't remove the 7.0a2 ones until we update mozilla.com/channels)
I followed the instruction in Comment 8, csb and sw builds are now added. Setting resolution to VERIFIED FIXED. Thank you Nick for the guidelines.
Status: RESOLVED → VERIFIED
Just had to push these two to aurora again, because they got lost in the last merge day :-(, http://hg.mozilla.org/releases/mozilla-aurora/pushloghtml?changeset=5a476aaaf4d9 Christian, any idea on how to prevent that?
Add it to the checklist and we'll make sure they stay in (https://wiki.mozilla.org/Releases/Merge_Checklist).
I made sure to transplant this correctly today
You need to log in before you can comment on or make changes to this bug.