Comment 13 for bug 1996653

Hi there,

I can confirm that Firefox is not released progressively. Once the release is out, all clients will get it on their next refresh (i.e. as fast as possible).

That said, in this case we were experiencing abnormally high network load which together with an actual network issue, required applying an emergency rate-limiting mechanism to allow us to cope with the extra traffic.

Since this mechanism is used only in emergencies, it's a bit rough around the edges, and I would prefer to devote our energies to improving the official progressive release system; with that in mind, some of the suggestions in this bug make sense and we'll be sure to take them into account as we make the progressive release feature more widely available.

One other thing: Liam said:

"The rollout ideally shouldn't occur if the user is running `snap refresh` manually. If a user is doing that, they may have a good reason why they want the latest release."

Doing a manual "snap refresh" should work as you describe and fully bypass throttling, however we just discovered that this feature was disabled on our side due to snapd not being compatible with it yet. As it happens, a snapd version that properly supports this was released last week, so we will be able to activate the "snap refresh bypasses throttling" thing at some point next week.

Per the above I'm marking this bug won't fix, but we plan to keep these requests in mind as I mentioned.