Bug statuses

Differences between revisions 11 and 12
Revision 11 as of 2007-07-20 22:47:32
Size: 2856
Editor: c-24-21-231-115
Comment:
Revision 12 as of 2007-09-05 20:08:49
Size: 2819
Editor: 67
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
The status of a bug report can be modified by clicking on the package name, in the yellow line and under the "Affects" column header, which will reveal a sub menu. You can then choose a new status in the drop down box. The status of a bug report can be modified by clicking on the current status in the yellow line, which will reveal a sub menu. You can then choose a new status in the drop down box.

Bug statuses are a reflection of the current state of a bug report. The state is a way to reflect the current progress of the bug report.

The status of a bug report can be modified by clicking on the current status in the yellow line, which will reveal a sub menu. You can then choose a new status in the drop down box.

Below is a list of bug statuses, their meaning and when to use them:

  • New:

    • Bugs are submitted with this status,
    • They sometimes lack information and

    • All of them should be untriaged
  • Incomplete:

  • Invalid:

    • Bugs marked as Invalid are closed and no longer show up in default searches

    • Be sure to triple-check a bug before you reject it
  • Confirmed:

    • Someone believes that that the report describes a genuine bug in enough detail that a developer could start working on a fix
    • Confirmed bugs require confirmation from someone other than the original reporter

    • This helps ensure that the bug is applicable to Ubuntu in general, and not a problem with the reporter's system, therefore...
    • Please don't confirm your own bugs!
  • Triaged:

    • A member of Ubuntu QA believes that the report describes a genuine bug in enough detail that a developer could start working on a fix
    • Use this when you are confident that it should be looked at by a developer and has enough information

  • In Progress:

    • If you are working on fixing a bug, set it to In Progress so people know what's going on

    • In Progress bugs should be assigned to the person working on them

  • Fix Committed:

    • For upstream projects, the fix is in CVS/SVN/bzr or commited to some place
    • For package maintainers, the changes are pending and to be uploaded soon (it's what PENDINGUPLOAD was in Bugzilla)
    • Fix Committed is also used when an updated package exists in a -proposed repository i.e. feisty-proposed

    • Fix Committed is not to be used when a patch is attached to a bug

  • Fix Released:

    • For upstream projects, a release tarball was announced and is publicly available
    • For package maintainers, a fix was uploaded to an official Ubuntu repository
      • This does not include -proposed i.e. feisty-proposed

      • Please don't hesitate to add a changelog as a comment, so people know what to look out for


CategoryBugSquad

Bugs/Bug statuses (last edited 2016-10-03 15:32:33 by es20490446e)