Account confirmers, Anti-spam team, canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,083
edits
CrashKill/Topcrash: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 18: | Line 18: | ||
* Bugs that spearhead investigation or fixes across a large collection of crashes | * Bugs that spearhead investigation or fixes across a large collection of crashes | ||
** Judging this needs engineering expertise - if fixing a bug would clean out a number of crashes (with differing signatures) that would be in similar volume to signatures matching other topcrash criteria, that bug itself qualifies for topcrash as well. | ** Judging this needs engineering expertise - if fixing a bug would clean out a number of crashes (with differing signatures) that would be in similar volume to signatures matching other topcrash criteria, that bug itself qualifies for topcrash as well. | ||
* Crashes for actions that users are rarely taking, even if they are somewhat out of the usual topcrash ranges | |||
** This needs feeling and expertise as well, thing like that can be e.g. printing crashes in the top 50 on desktop release and similar cases. | |||