Closed Bug 918320 Opened 11 years ago Closed 11 years ago

[B2G] Add bg, bn-BD, it, mk, zh-CN to v1.2 builds

Categories

(Firefox OS Graveyard :: General, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:koi+, firefox26 fixed, b2g-v1.2 fixed)

VERIFIED FIXED
blocking-b2g koi+
Tracking Status
firefox26 --- fixed
b2g-v1.2 --- fixed

People

(Reporter: delphine, Assigned: mozilla)

References

Details

(Whiteboard: l10n)

According to the bug tracking all required languages for v1.2, Italian and Bulgarian have been requested: see Bug 905292

However, I have noticed that Italian and Bulgarian do not appear on our internal builds. Please add both to languages_dev.json
blocking-b2g: --- → koi?
Updating bug. As per Bug 905292, Simplified Chinese has also been requested.
Please also add zh-CN to our v1.2 builds.

(Italian: it
Bulgarian: bg)
Summary: [B2G] Add Bulgarian and Italian to v1.2 builds → [B2G] Add all requested shipping locales to v1.2 builds
we'll need repos and mirroring for zh-CN, so we shouldn't jump on that yet. Filed bug 918367.
Macedonian (mk) also missing
Pike,

When will the mirroring complete?
Flags: needinfo?(l10n)
Whiteboard: l10n
The repos and mirrors were created in bug 918367.

The locales are about 88k each in terms of profile size. I think that should be good to take. That's just the l10n, not keyboards etc.
Depends on: 918367
Flags: needinfo?(l10n)
Summary: [B2G] Add all requested shipping locales to v1.2 builds → [B2G] Add bg, bn-BD, it, mk, zh-CN to v1.2 builds
Pike what are the next steps here given 918367 is resolved.
Flags: needinfo?(l10n)
I guess that it'd be helpful to have bug 924575 (v1.1 branching for l10n) out of the way, but the next steps are changing the languages_dev.json on both master and v1.2 branch, and languages_all.json on v1.2.
Depends on: 924575
Flags: needinfo?(l10n)
(In reply to Axel Hecht [:Pike] from comment #7)
> I guess that it'd be helpful to have bug 924575 (v1.1 branching for l10n)
> out of the way,

recently approved. landing away. 
> but the next steps are changing the languages_dev.json on
> both master and v1.2 branch, and languages_all.json on v1.2.
https://github.com/mozilla-b2g/gaia/pull/12765
r?
Flags: needinfo?(l10n)
(In reply to Axel Hecht [:Pike] from comment #7)
> I guess that it'd be helpful to have bug 924575 (v1.1 branching for l10n)
> out of the way, but the next steps are changing the languages_dev.json on
> both master and v1.2 branch, and languages_all.json on v1.2.

per b2g meeting w/clee just now, explicitly Italian is *not* needed on v1.1HD. That lines up with what we have here, with Italian on v1.1 and coming soon to v1.2 and master. I'm noting explicitly to avoid possible future concern about v1.1HD.
(In reply to delphine from comment #3)
> Macedonian (mk) also missing

I don't believe a repository creation request was ever made for Macedonian, since comment 3 was made after bug 918367 was resolved.
axel: 

per clee, whenever we land a new locale in a given branch, we need to enable that locale on all newer branches (in this specific case, adding a locale to v1.2 means also adding it to v1.3/master). This helps with updates, amongst other things. I dont know if thats written down as explicit written policy someplace, but its been done in the past - bug#838516 is one example.

Given that, I'd initially thought we'd just morph this bug#918320 to also including enabling these locales on master. After all, thats what happened in bug#838516. However, after bug#918316#c5, if you prefer us to file separate bug to track enabling these-same-locales-on-master, let us know and we'll do that.
blocking-b2g: koi? → koi+
blocking-b2g: koi+ → -
Is this a meta bug? If not, it should be koi+
Leaving this in the koi? queue until we figure out if this is a meta bug or not.
blocking-b2g: - → koi?
mk repos are up, please land the PR for the 1.2 locales. All the other stuff in this bug is really just confusing me.
Flags: needinfo?(l10n)
Landed.
Sounds like we can close this then. Closing this out.

Also marking koi+ as this isn't a tracker bug per Pike's comments - it's required build changes for the 1.2 locales.
Status: NEW → RESOLVED
blocking-b2g: koi? → koi+
Closed: 11 years ago
Resolution: --- → FIXED
Verified on Buri device, using today's latest v1.2 Com RIl
Marking as verified fixed
Status: RESOLVED → VERIFIED
blocking-b2g: koi+ → koi?
I'm assuming you didn't mean to flip the affected flag & blocking flag.
blocking-b2g: koi? → koi+
No I didn't. It's really weird because I touched absolutely nothing and just changing the bug to resolved fixed did that. Was wondering if that was normal...(and apparently it's not)
Assignee: nobody → aki
You need to log in before you can comment on or make changes to this bug.