With the rapid release cycle, we're either doing nightlies or release builds. In that scenario, it makes sense to just have a single file that controls both the list of locales to get built, and the platforms it ships on. Wherever we parse all-locales right now, we should support trailing platform lists like de ja linux win32 ja-JP-mac mac ko
We could also follow the mobile json format, if we wanted consistency. I'm not tied to it, though.
With bug 863334, that format ties closely to mobile now, and it's also including revisions, which I'd rather not check in, neither hashes nor tags.
Component: Infrastructure → Automation
Product: Mozilla Localizations → Localization Infrastructure and Tools
You need to log in before you can comment on or make changes to this bug.