We'll need localized builds for b2g for testing and eventually, for shipping. This is similar to bug 761868. 1) the initial list of locales is en-US, es, pt-BR, but we want to make sure it can be easily extended with more locales. Scalability is very important to us and we will want to 2) single locale or multilocale? what are the requirements for Basecamp here? 3) Kaze, I recall you wrote a script that concatenates per-locale .properties into a single file. We might need that, depending on the outcome of the discussion that's currently taking place in mozilla.dev.gaia. 4) the repositories to pull localization from are TBD: it might be hg, or git, depending on the exact approach that we choose (this is related to #3) 5) Should this block bug 763611 and bug 744008? 6) Should I file another bug for localized desktop builds?
Assigning to John for prioritization.
until there is wide availability of devices we will need desktop builds in an emulator to check out things like dialog sizes and screens fitting in the form factor.
grabbing while sorting out various B2G priorities in https://etherpad.mozilla.org/b2g-builds.
Just got out of a call with Staś and Axel. These are the details as I understand them: * these will be repacks of desktop b2g builds because that is the easiest thing for localizers to test * these will be single locale repacks and there will be up to 40 of them (40 localization teams currently) * the gecko repack process is largely borrowed from mobile ** make targets (chrome-%?) already exist AIUI * Gaia repack process is still TBD, although we don't expect to be repacking Gaia in the traditional sense. Likely dropping in bundles. ** there are experiments going on here to determine what the best path forward is because string substitution is slow on the client side. We probably can't include more than one Gaia locale bundle in a given repack. Even 3-4 locales is unreasonably slow at present. ** can we pass a local list to build/zip-webapps.js? * localizers are working out of hg repos (for Gecko, I assume) * l10n-changesets? ** probably same as for mobile/desktop: dashboard -> buildbot-configs ** "borrow" sign-offs from mobile * likely won't need shipped_locales ** list of locales will be specified per-carrier
Clearing blocker nom on tracking bug. All deps are either +'d or -'d.
All of the required localized builds are now ready. See dep bugs for details.