Drop the "Has Regression Range" field as no longer necessary
Categories
(bugzilla.mozilla.org :: Administration, task)
Tracking
()
People
(Reporter: marco, Assigned: dkl)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
Since we introduced the "Regressed By" field, "Has Regression Range" is not as useful anymore.
There are still cases where we have a regression range and no clear regressor, but is there any benefit in knowing that there is a regression range directly from a field?
Assignee | ||
Comment 1•2 years ago
|
||
This is a list of products we currently have the field enabled:
qr/^cf_has_regression_range$/ => {
"Core Graveyard" => [],
"Core" => [],
"DevTools Graveyard" => [],
"DevTools" => [],
"External Software Affecting Firefox" => [],
"Firefox Build System" => [],
"Firefox for Android Graveyard" => [],
"Firefox for Android" => [],
"Firefox for iOS" => [],
"Firefox Graveyard" => [],
"Firefox" => [],
"GeckoView" => [],
"NSS" => [],
"Tech Evangelism Graveyard" => [],
"Tech Evangelism" => [],
"Toolkit Graveyard" => [],
"Toolkit" => [],
"WebExtensions" => [],
},
We would need to make sure that all products are file with turning it off completely or we can narrow down the list. The current values for the field would still be in the DB but the field would just no longer be visible.
Reporter | ||
Comment 2•2 years ago
|
||
There was no disagreement in dropping the field, https://groups.google.com/a/mozilla.org/g/dev-platform/c/BSrur7jYfN8, so I went ahead and updated the autonag bot not to set nor use the field anymore in https://github.com/mozilla/relman-auto-nag/pull/1495.
I think we can now disable the field.
Assignee | ||
Comment 3•2 years ago
|
||
Field has been disabled. I will also remove the code that dictates visibility and create a PR for the change.
Assignee | ||
Comment 4•2 years ago
|
||
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 5•2 years ago
|
||
Description
•