Veridian 3

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.

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
    • V3-dupecrash: 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.
  • V3-trends: Improve Trend Reports to identify and alert teams about Explosive bugs
• Further tags:
  • V3-todo: Bugs that still need triage/classification
  • V3-infra: Strictly infrastructure issues, not crash analysis itself
  • V3-UI: User Interface issues