Redirect existing Belarusian (be) users to Russian (ru) builds via update snippets

RESOLVED FIXED

Status

RESOLVED FIXED
2 years ago
2 years ago

People

(Reporter: flod, Assigned: rail)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment, 1 obsolete attachment)

(Reporter)

Description

2 years ago
We plan to stop building Beta and Release for Belarusian (be). 

The agreement with BD is to move the existing users to Russian (ru) through the update system. We don't need to build a special repackage for these users, just to move them to a full Russian build.
(Reporter)

Comment 1

2 years ago
Created attachment 8802903 [details] [diff] [review]
patch for mozilla-aurora

This patch removes be from aurora builds (all-locales), and beta/release (shipped-locales).
Attachment #8802903 - Flags: review?(lebedel.delphine)
(Reporter)

Comment 2

2 years ago
Comment on attachment 8802903 [details] [diff] [review]
patch for mozilla-aurora

Sorry, clearly wrong bug :-\
Attachment #8802903 - Attachment is obsolete: true
Attachment #8802903 - Flags: review?(lebedel.delphine)
Assignee: nobody → mtabara
Adding this back to the pool.
Assignee: mtabara → nobody
(Assignee)

Comment 4

2 years ago
Francesco, do we need to show a What's New Page for these users?
Flags: needinfo?(francesco.lodolo)
(Assignee)

Comment 5

2 years ago
Created attachment 8819014 [details]
Firefox-51.0b7-build1-Redirect-be-to-ru.json

I created a release blob based on latest beta (51.0b7):

* removed all locales, except "ru"
* removed all "partials"
* removed all channels except "*"
* s/%LOCALE%/ru
* replaced locales.ru with locales.be
* created a new rule on beta-cdntest to match "be" and serve this update

I installed one of the 50 betas in a win64 VM, changed the channel to "beta-cdntest" and updated it to "ru" as expected. If someone can verify this on other platforms, we can move this rule to the beta channel.
Assignee: nobody → rail
(Reporter)

Comment 6

2 years ago
(In reply to Rail Aliiev [:rail] ⌚️ET from comment #4)
> Francesco, do we need to show a What's New Page for these users?

I'd say no, given that we don't have such a page available on mozilla.org, nor a community to localize it in Belarusian.
Flags: needinfo?(francesco.lodolo)
(Assignee)

Comment 7

2 years ago
Francesco, I can enable this on the bet channel anytime. How hard do you wan to QA this? Is QA I made in comment 5 sufficient?
Flags: needinfo?(francesco.lodolo)
(Reporter)

Comment 8

2 years ago
(In reply to Rail Aliiev [:rail] ⌚️ET from comment #7)
> Francesco, I can enable this on the bet channel anytime. How hard do you wan
> to QA this? Is QA I made in comment 5 sufficient?

Can you explain in details how I can test it (in particular how to set the update channel to "beta-cdntest")? I might give it a try just to check.
Flags: needinfo?(francesco.lodolo)
(Assignee)

Comment 9

2 years ago
This is what I did:

* download one of the older "be" installers, let's say 50.0b6
* disconnect the VM from the network to prevent accidental background updates
* install Firefox
* in about:config change "app.update.log" to true to log update URLs etc in case I want to debug something (not usually required)
* close Firefox
* edit "defaults\pref\channel-prefs.js" in the app directory (c:\Program Files\...). s/beta/beta-cdntest/.
* Launch Firefox
* Open the console (Ctrl+J IIRC) to see the debug  messages (not usually required)
* Enable networking
* Check for updates, apply the update, restart Firefox.
* Check the UI, maybe omni.ja for locale settings.

I hope this helps.
(Reporter)

Comment 10

2 years ago
Thanks. I did a test on Linux and Mac, starting from a random 50 beta, and it works as expected. Updates to a Russian build, general.useragent.locale is set to ru instead of be, search settings are from Russian version.

I think we can move on. I'll try to keep a look on Telemetry to see if users actually move away from Belarusian.
(Assignee)

Comment 11

2 years ago
This is live now. I'll keep the bug around to do the same for the release channel in 51.x.
(Assignee)

Comment 12

2 years ago
This is live on the release-cdntest channel now. I repeted the steps in comment 9 using 50.0.2 be and it worked fine. I'll move this rule to the release channel after we release.
(Assignee)

Comment 13

2 years ago
This is live on the release channel now at 25% (to match the main rule). I tested it in a VM and updated from 50.0.2 be to 51.0.1 ru. I'll set it to 100% when we unthrottle 51.0.1
(Assignee)

Comment 14

2 years ago
100% now
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
(Assignee)

Comment 15

2 years ago
I deleted the rule to simplify the current rules.
You need to log in before you can comment on or make changes to this bug.