Closed Bug 1535299 Opened 8 months ago Closed 8 months ago

Remove stale locales from Firefox desktop builds in Firefox 68

Categories

(Firefox Build System :: General, enhancement)

enhancement
Not set

Tracking

(relnote-firefox 68+, firefox68 fixed)

RESOLVED FIXED
mozilla68
Tracking Status
relnote-firefox --- 68+
firefox68 --- fixed

People

(Reporter: flod, Assigned: flod)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

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.

: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?

Flags: needinfo?(francesco.lodolo)

(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.

Flags: needinfo?(francesco.lodolo)

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.

Blocks: 1539799
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
Status: NEW → RESOLVED
Closed: 8 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla68
Blocks: 1540379

Removals done on elmo for fx_central.

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)]: -

relnote-firefox: --- → ?
See Also: → 1557461

This is in the 68.0beta desktop release notes.

Blocks: 1582720
You need to log in before you can comment on or make changes to this bug.