Closed
Bug 1391013
Opened 7 years ago
Closed 4 years ago
require fallbackMapping when backgroundRate is <100?
Categories
(Release Engineering Graveyard :: Applications: Balrog (backend), enhancement, P3)
Release Engineering Graveyard
Applications: Balrog (backend)
Tracking
(Not tracked)
RESOLVED
MOVED
People
(Reporter: bhearsum, Unassigned)
Details
(Whiteboard: [lang=python])
Now that it exists, fallbackMapping is something we almost always use when running a throttled rollout. I can't think of any case where we'd want users to go no updates instead of the previously released version during these times. We should consider enforcing this in the backend, and rejecting any requests to change backgroundRate to <100 unless fallbackMapping is set, or is getting set as part of the change. We'll need to ensure that these would actually work for all different types of updates (GMP, SystemAddons, Firefox) before deciding to move forward.
|
Reporter | |
Comment 1•7 years ago
|
||
I'm unassigning this because it's a lower priority bug that I don't have time to mentor right now. There's also been some discussion elsewhere (that I should've put here) that makes it unclear whether we want to move forward with it.
Assignee: daniel.kitui → nobody
|
|
Reporter | |
Comment 2•4 years ago
|
||
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → MOVED
|
||
Updated•4 years ago
|
Product: Release Engineering → Release Engineering Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•