Remove stale locales from Firefox desktop builds in Firefox 68
Categories
(Firefox Build System :: General, enhancement)
Tracking
(relnote-firefox 68+, firefox68 fixed)
People
(Reporter: flod, Assigned: flod)
References
Details
Attachments
(1 file)
|
Bug 1535299 - Remove locales from Nightly and Beta build of Firefox desktop (as, en-ZA, mai, ml, or)
47 bytes,
text/x-phabricator-request
|
Details | Review |
We have a few stale locales that haven't seen contributions in months, and want to use the ESR build to remove them and redirect users to another locale.
List of locales: as, en-ZA, mai, ml, or.
I'll file a different bug to create Balrog rules to redirect them to en-GB once we land.
|
||
Comment 1•5 years ago
|
||
:flod, all of these locales will go to en-GB?
Do we want to "bikeshed" the users even for nightly (e.g. 68.0a1 <buildID X> en-ZA --> 68.0a1 <buildID Y> en-GB) - Do we have or want any What's New Page or First Run experience to tell these users what happened/changed?
|
Assignee | |
Comment 2•5 years ago
|
||
(In reply to Justin Wood (:Callek) from comment #1)
:flod, all of these locales will go to en-GB?
4 are indic locales, so en-GB seems to make more sense than en-US. Also, we are not talking about a significant number of users.
en-ZA is the only large one in terms of users. From a practical point of view, I don't think users should notice the difference between en-GB and en-ZA, and (again) I believe that's better than redirecting them to en-US.
If there are concerns about dropping en-ZA, for example for partner reasons, we could leave it around, but it's really unmaintained (and it's been for years).
Do we want to "bikeshed" the users even for nightly (e.g. 68.0a1 <buildID X> en-ZA --> 68.0a1 <buildID Y> en-GB) - Do we have or want any What's New Page or First Run experience to tell these users what happened/changed?
I don't think we can have a WNP or Firstrun, for sure my team doesn't have cycles or resources to do that. We're going to relnote removal in 68 release.
|
|
Assignee | |
Comment 3•5 years ago
•
|
||
To answer your other question: yes, I think we should redirect users also on Nightly and Beta, and drop the rules in 1 or 2 cycles.
|
|
Assignee | |
Comment 4•5 years ago
|
||
Pushed by opoprus@mozilla.com: https://hg.mozilla.org/mozilla-central/rev/c8763665035c Remove locales from Nightly and Beta build of Firefox desktop (as, en-ZA, mai, ml, or) r=Callek
|
||
Comment 6•5 years ago
|
||
| bugherder | ||
|
||
Comment 7•5 years ago
|
||
Removals done on elmo for fx_central.
|
|
Assignee | |
Comment 8•5 years ago
|
||
Release Note Request (optional, but appreciated)
[Why is this notable]: Removing a few unmaintained localizations from builds. The removal is happening for Firefox 68 and will ride the trains.
[Affects Firefox for Android]: No
[Suggested wording]: Removed unmaintained languages: Assamese (as), English - South Africa (en-ZA), Maithili (mai), Malayalam (ml), Odia (or). Existing users are migrated to the British English (en-GB) version of Firefox.
[Links (documentation, blog post, etc)]: -
Description
•