States

Revision 10 as of 2007-02-15 05:44:23

Clear message

Wiki edit: BugStates Procedures

[asac]: draft for discussion - still a stub

Introduction

Bug state should only be modified according to this definition.

Usually non-team-members are discouraged to change states on their own without getting in contact with the MozillaTeam first.

In case a user does not know about this document, be nice. For instance, if a MozillaTeam member recognizes that a user did wrongly confirm a bug, point him to this document and fix the state again.

States and Uses

Each bug will more or less run through the following states in its life. The goal be to make all bugs eventually end up in one of our two final states:

  • Rejected - the bug could not be processed
  • Fix Released - the bug has been fixed

unconfirmed

Bugs in state 'unconfirmed'

Aliases

  • Initial Contact
  • Screening
  • Categorization

Description

Bugs are initially submitted in state 'unconfirmed'. Unconfirmed bugs have not yet been screened and categorized successfully.

Goals

  • Minimize initial response time
  • Categorize to initiate workflow in the proper direction
  • Filter obvious duplicates
  • Deliver an initial professional support experience for the bug reporter
  • Fix bad bug titles (like 'firefox crashes') if more information is available in bug description

Skill Level Requirements

  • No first timer
  • To properly initiate the bug workflow you need a good understanding of the ["MozillaTeam/Bugs/Procedures"]
  • For duplicate detection you need the more or less bug picture of bugs already reporter

Activities/Tags

  • <none> - Absence of a state tag indicates that the bug has not yet been triaged

needs info

Aliases

  • Initial Contact
  • Screening
  • Recategorization

Description

Bugs that require more input from the user or some work from MozillaTeam triagers in order to make a bug useful for further processing in state 'confirmed' are kept in state 'needs info'.

Goals

  • Gather information needed to properly process the bug in state 'confirmed'
  • Improve bug title and description with input from reporter
  • Get fully traced crash reports for crashers bugs
  • Identify testcases to reproduce feature bugs
  • Reproduce feature bug testcases. At best the tester would be someone in the MozillaTeam or someone else who is responsive upon request - at best regularly lurking on IRC.

  • Filter duplicates as discussion and description of a bug evolves.

Skill Level Requirements

  • We have tasks for Beginners as well as Experienced Bug Triagers here.

Activities/Tags

(See ["MozillaTeam/Bugs/Tags"] for a detailed description on tags, their meaning as well as typical actions associated with them)

  • <none> - this is illegal, aka a triage bug: state need info always needs one of the tags below. If there is a bug that does not fit, talk to us in order to find a new one.

  • For Crashers:
    • mt-needreport - we need a useful crash report from the user
    • mt-needretrace - we need someone to do a retrace of not yet processed crash report submitted in the bug
  • For feature bugs:
    • mt-needtestcase - we need a step by step description on how to reproduce
    • mt-needtester - we need a tester which can provide responsive feedback at best in irc channel
  • All bugs:
    • mt-needinfo - we need additional information before proceeding with bug evaluation.
    • mt-needsummary - we need someone to clean up the issue summary before proceeding.

confirmed

Aliases

  • Evaluation
  • Assign

Description

A bug contains all information needed to reproduce, triage/submit upstream or write a solution on our own.

Goals

Skill Level Requirements

Activities/Tags

in progress

Aliases

  • bug fixing

Description

Bug is processed upstream or we are currently implementing a solution.

Goals

Skill Level Requirements

Activities/Tags

fix committed

Aliases

  • testing

Description

Bug has a fix submitted, which can be tested upstream or in a MozillaTeam/PreviewPackage.

Goals

  • verify the fix corrects the initially reported problem
  • verify the fix causes no regressions

Skill Level Requirements

Activities/Tags

  • needtesting

fix released

Bug fix has been released as an official package to ubuntu distribution archive.


[:CategoryMozillaTeam]