Bug statuses

Differences between revisions 1 and 2
Revision 1 as of 2007-07-17 23:46:31
Size: 2618
Editor: c-24-21-231-115
Comment: Copy from Bugs/CommonTasks to pages less lengthy
Revision 2 as of 2007-07-17 23:55:48
Size: 2701
Editor: c-24-21-231-115
Comment: Added comment about bugs with patches
Deletions are marked like this. Additions are marked like this.
Line 31: Line 31:
  * {{{Fix Committed}}} is '''not''' to be used when a patch is attached to a bug

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.

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:

    • If you have to ask the reporter questions, set the bug to Incomplete

    • Ask the submitter to provide any necessary information in a comment, and make sure you assign the bug to yourself so you will get the response.
    • a regular task for Incomplete bugs is to follow up and if there are no answers after a reasonable stage (a month), close them (as Inavild ) using the [:Bugs/Responses#head-6ee6466fdaac8c81274185f0316afd794d2ee0b6:Old Incomplete Response].

  • 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

Bugs/Bug statuses (last edited 2024-07-02 15:33:21 by dbungert)