Veridian 3: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 2: | Line 2: | ||
In the same spirit, the project I internally dub "Veridian 3" is about dealing with crashes to make the bad ones preventable and other ones more controllable, all through prioritizing Socorro work. | In the same spirit, the project I internally dub "Veridian 3" is about dealing with crashes to make the bad ones preventable and other ones more controllable, all through prioritizing Socorro work. | ||
== Bugzilla Tags === | |||
For classification of Socorro bugs, I will in the beginning use private tags starting with "V3", and those will be documented here. | For classification of Socorro bugs, I will in the beginning use private tags starting with "V3", and those will be documented here. |
Revision as of 00:47, February 18, 2011
On a planet called Veridian III, a decisive battle was fought to prevent a future firing of a rocket into a star that would change gravitational forces and make "the nexus" crash into the planet as well as destroy the planet with a shock wave. Preventing this catastrophy made the crash of the USS Enterprise on the planet controllable as to suffer no human casualties.
In the same spirit, the project I internally dub "Veridian 3" is about dealing with crashes to make the bad ones preventable and other ones more controllable, all through prioritizing Socorro work.
Bugzilla Tags =
For classification of Socorro bugs, I will in the beginning use private tags starting with "V3", and those will be documented here.
- Contract areas:
- V3-integrity: Improving Crash Data Integrity
- Identification and Removal of Duplicate Crash reports
- V3-search: Improving Search Capabilities
- V3-classify: Improving Classification and Characterization of Crash Reports and Improved Signature Generation
- V3-correlation: additional correlation reports to help identifying circumstances around the crash and steps to reproduce. [tag includes everything on correlations]
- V3-trends: Improve Trend Reports to identify and alert teams about Explosive bugs [tag includes all trend reports]
- V3-integrity: Improving Crash Data Integrity
- Further tags:
- V3-todo: Bugs that still need triage/classification
- V3-infra: Strictly infrastructure issues, not crash analysis itself
- V3-UI: User Interface issues
- V3-notify: Notifications (to be) sent out by the Socorro system
- V3-config: Configuration adaptations (skiplist additions, etc.)
Comments From Socorro Users
<wsmwk> KaiRo: second tier needs might be bug 421119, bug 518823, bug 578376, bug 411354. third tier: bug 527304, bug 512910, better workflow for updating skiplist) <firebot> Bug https://bugzilla.mozilla.org/show_bug.cgi?id=421119 min, P3, 2.1, nobody, NEW, function for socorro to compare stacks of two or more crash reports <firebot> Bug https://bugzilla.mozilla.org/show_bug.cgi?id=518823 enh, --, Future, nobody, NEW, indicate bug's status for bugzilla keyword topcrash <firebot> Bug https://bugzilla.mozilla.org/show_bug.cgi?id=578376 nor, --, ---, nobody, NEW, multiple crashes from a single person should have less weight then many crashes from different peopl <firebot> Bug https://bugzilla.mozilla.org/show_bug.cgi?id=411354 nor, P1, 2.0, nobody, REOP, Add ability to search by build ID <firebot> Bug https://bugzilla.mozilla.org/show_bug.cgi?id=527304 enh, --, ---, nobody, REOP, provide smart analysis ala talkback