We still use this file in multiple places, but the real source of truth is the l10n chagesets used in ship-ip, copied from the l10n dashboard. Pros: * No need to edit that file as a part of merge if we have beta-only locales * Only one source of truth for reals \o/ Cons: * There may be some external consumers of this files. Can be substituted with http://ftp.mozilla.org/pub/firefox/candidates/47.0.1-candidates/build1/l10n_changesets.txt

Historic background: shipped-locales used to be very useful when we had various locales that we didn't want to ship on all platforms, due to various problems with font support. Those days are over, sung to some well known tune. The only left-over is ja-JP-mac, and I'm OK with hard-coding that part in build/release automation. Thus, sounds like a good idea to me.

We have moved to l10n-changesets.json, which uses shipped-locales to determine which locales to include. I think this is a good situation. If we want changes to the bumper's behavior, we can revisit.