Closed
Bug 823008
Opened 12 years ago
Closed 12 years ago
Don't send dev.tree-management Talos emails for improvements
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: emorley, Assigned: emorley)
Details
(Keywords: sheriffing-P1)
Attachments
(1 file)
2.30 KB,
patch
|
Details | Diff | Splinter Review |
Until datazilla is up and running, I'm stuck with checking dev.tree-management. At the moment, it send emails for both regressions & improvements. To reduce the noise I propose we stop sending for improvements, given that: a) Most of the emails are false positives anyway b) If something causes a regression and then is backed out, we can see the corresponding correction on graphs.m.o without the need for extra emails.
Assignee | ||
Updated•12 years ago
|
Summary: Don't send dev.tree-management regression emails for improvements → Don't send dev.tree-management Talos emails for improvements
Assignee | ||
Comment 1•12 years ago
|
||
Comment 2•12 years ago
|
||
How many developers expect to see the improvement notices for changes that should give performance gains? Would the lack of the notices be a surprise for them?
Comment 3•12 years ago
|
||
I have been closely monitoring the dev.tree-management emails for Android (only, thankfully!) for several months and using them for tracking both regressions and improvements. I can live without the improvement notices, but they are useful to me. Would it help if we changed the message titles to better distinguish improvements from regressions? ** REGRESSION ** (improvement)
Assignee | ||
Comment 4•12 years ago
|
||
Sure I guess I could just add that to bug 823016 so it's clearer by default (and for me, filter the improvement emails to trash).
Assignee | ||
Updated•12 years ago
|
Attachment #693823 -
Flags: review?(catlee)
Assignee | ||
Updated•12 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•