Closed
Bug 1355232
Opened 9 years ago
Closed 9 years ago
remove :hwine from being qa on all components
Categories
(bugzilla.mozilla.org :: Administration, task, P1)
Tracking
()
RESOLVED
FIXED
People
(Reporter: hwine, Assigned: emceeaich)
Details
similar to bug 1323585 - I should be removed as default QA for any component where I am it. Likely all in the Release Engineering product.
Related - I will then need reset to "default QA" all the bugs for which I'm listed as QA contact. I can do that via the normal UI, but (no longer?) see the "don't send email" checkbox. Any guidelines on that?
| Assignee | ||
Updated•9 years ago
|
Assignee: nobody → ehumphries
Priority: -- → P1
| Assignee | ||
Comment 1•9 years ago
|
||
:jmaher who would be taking these over from Hal?
I'd like to update this in one go.
Flags: needinfo?(jmaher)
Comment 2•9 years ago
|
||
I am not sure here, I believe Hal was default on many of the release engineering components- we should get a more concrete list- I am going with :catlee for now, but I suspect this means taking a list of all releng bugzilla components and picking who is the default QA
I see:
balrog: frontend
balrog: backend
buildduty
general automation
loan requests
mozharness
other
platform support
release automation
releases
releases: custom builds
ship it
tools
tree status
:catlee, can you comment on who should be default QA for each of those components and maybe who should be triage owner as well :)
Flags: needinfo?(jmaher) → needinfo?(catlee)
Comment 3•9 years ago
|
||
I think default QA and triage owner should be the same. We don't really use either of those fields in any case!
See also bug 1351713 for merging Other and Tools into General.
I can be default QA / triage owner for any components that Hal was responsible for.
Flags: needinfo?(catlee)
| Assignee | ||
Comment 4•9 years ago
|
||
I believe I've removed Hal from all the things. If he shows up as default QA somewhere, then open a new bug.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•