Closed
Bug 466720
Opened 16 years ago
Closed 15 years ago
Stop automatically processing reports for old versions after a few days
Categories
(Socorro :: General, task)
Socorro
General
Tracking
(Not tracked)
RESOLVED
WONTFIX
1.2
People
(Reporter: samuel.sidler+old, Unassigned)
References
Details
As I mentioned in bug 466528 comment 0, we should stop processing reports for old versions after we freeze topcrash reports (bug 466528). The exception is crash reports that enter the priority processing queue, which should get processed regardless of version. This depends on having the ability to freeze topcrash reports.
Comment 1•15 years ago
|
||
this would also reduce load on server
Updated•15 years ago
|
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
Comment 3•15 years ago
|
||
Reopening - this is still a separate issue from bug 466528.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Comment 5•15 years ago
|
||
We should be able to do this with the admin panel and the CRUD page for branches/versions.
Updated•15 years ago
|
Target Milestone: --- → 1.2
Comment 6•15 years ago
|
||
Note: Not sure if this is actually dependent on the collector.
Comment 7•15 years ago
|
||
yes, this is very dependent on the collector. Providing a way to quickly disregard a prod/version is one of my improvements to the collector in Bug 521362 that needs to be addressed before FF3.6 ships and the collector volume goes up. Another complication is making the collector configuration easy to administer. While it would be nice to have the admin/CRUD page for this configuration, the collectors don't have database access.
Comment 8•15 years ago
|
||
We're not concerned about load on the server, and we don't want to stop processing reports in case that data is needed to spot trends in versions that people are still using.
Status: REOPENED → RESOLVED
Closed: 15 years ago → 15 years ago
Resolution: --- → WONTFIX
Assignee | ||
Updated•12 years ago
|
Component: Socorro → General
Product: Webtools → Socorro
You need to log in
before you can comment on or make changes to this bug.
Description
•