Confirmed users
2,492
edits
| Line 13: | Line 13: | ||
** We often have the need to generate a number of manual reports to help analyze and diagnose a particular issue. Kairo has many in his own [https://crash-analysis.mozilla.com/rkaiser/ directory]. | ** We often have the need to generate a number of manual reports to help analyze and diagnose a particular issue. Kairo has many in his own [https://crash-analysis.mozilla.com/rkaiser/ directory]. | ||
** Manual reports are often temporary until we can integrate them into Socorro. Other times we need a manual report to track a short-term issue. | ** Manual reports are often temporary until we can integrate them into Socorro. Other times we need a manual report to track a short-term issue. | ||
** We used a number of keywords in bugzilla to track crashes - <b>crash</b>, <b>topcrash</b>, <b>regression/ | ** We used a number of keywords in bugzilla to track crashes - <b>crash</b>, <b>topcrash</b>, <b>regression</b>, <b>regression</b>. You will see queries based on these flags in the wiki. | ||
** We also used a wide range of whiteboard tags to help us inventory crashes. Some like <b>[startupcrash]</b> are more recent and some like <b>[crashkill]</b>are old and not used that much any more. We will often use temporary tags to track crashes that correlate to a particular OS release. | ** We also used a wide range of whiteboard tags to help us inventory crashes. Some like <b>[startupcrash]</b> are more recent and some like <b>[crashkill]</b>are old and not used that much any more. We will often use temporary tags to track crashes that correlate to a particular OS release. | ||
** We also make use of a number of whiteboard tags as well. | ** We also make use of a number of whiteboard tags as well. | ||