Differences between revisions 2 and 4 (spanning 2 versions)
Revision 2 as of 2008-10-19 15:13:32
Size: 1700
Comment: add unloved query
Revision 4 as of 2009-05-19 19:31:01
Size: 1742
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 8: Line 8:
 * Testing - a patch is merged, but poster has not confirmed it works  * Testing - a patch is merged, but poster has not confirmed it works, or it didn't reach the main repo yet
Line 22: Line 22:
 * Sort open issues by priority and activity - here is a [http://www.selenic.com/mercurial/bts/issue?@columns=title,id,activity,status,assignedto&@sort=status,activity&@group=priority&@filter=status,priority,status,priority&@pagesize=100&@startwith=0&status=-1,1,3,5&priority=1,2,3&@dispname=triage triage] and a [http://www.selenic.com/mercurial/bts/issue?@columns=title,id,activity,priority,status&@sort=activity&@filter=status&@pagesize=100&@startwith=0&status=-1,1,2,3,4,5,6,7&@dispname=unloved unloved] query.  * Sort open issues by priority and activity - here is a [[http://www.selenic.com/mercurial/bts/issue?@columns=title,id,activity,status,assignedto&@sort=status,activity&@group=priority&@filter=status,priority,status,priority&@pagesize=100&@startwith=0&status=-1,1,3,5&priority=1,2,3&@dispname=triage|triage]] and a [[http://www.selenic.com/mercurial/bts/issue?@columns=title,id,activity,priority,status&@sort=activity&@filter=status&@pagesize=100&@startwith=0&status=-1,1,2,3,4,5,6,7&@dispname=unloved|unloved]] query.

Bug statuses and what they mean:

  • Unread - no one's ever responded to this bug (bad)
  • Deferred - we've decided not to deal with this problem now
  • Chatting - we're discussing a solution
  • Need-eg - we need more information to progress
  • In-progress - a partial fix exists
  • Testing - a patch is merged, but poster has not confirmed it works, or it didn't reach the main repo yet
  • Done-cbb - (could be better or couldn't be bothered) not perfect, but we've done as much as we're going to do
  • Resolved - problem is fixed

Priorities and what they mean:

  • critical - data loss or security issue
  • urgent - bug that is blocking development
  • bug - bug that's not blocking development
  • feature - it's not a bug, it's a feature
  • wish - would be nice

Triage

  • Sort open issues by priority and activity - here is a triage and a unloved query.

  • Diagnose issues and add appropriate people to the nosy list
  • Merge duplicates by setting superseder in the more recent bug, copy its nosy list to the older bug, and add a pointer to the new issue in the old issue if it contains new info
  • Improve bug titles to be more informative
  • Add appropriate categories
  • Set appropriate priorities (eg degrade urgent issues with workarounds to bug)

ManagingBugs (last edited 2015-03-11 18:18:47 by mpm)