Difference between revisions of "Bug Lists"

From Audacity Wiki
Jump to: navigation, search
(Tweak "Latest Changes for" queries)
(add suggested scheme for when/by whom a bug can be "resolved - fixed")
Line 26: Line 26:
 
{| width="90%" cellpadding="5px"
 
{| width="90%" cellpadding="5px"
 
|-
 
|-
|valign="top"|'''Open Bugs'''*
+
|valign="top"|'''Open Bugs'''
 
| 
 
| 
 
|valign="top"|'''Awaiting Developer Fix'''
 
|valign="top"|'''Awaiting Developer Fix'''
Line 62: Line 62:
  
  
<sup>*</sup>&nbsp;Bugs which have had a fix applied by a developer remain OPEN until RESOLVED by QA.  
+
== Workflow when resolving bugs ==
 +
* The current workflow is that when a bug has a fix applied by a developer, the developer should move the bug status to '''DEVEL - FIX MADE'''. This means the bug is still '''OPEN'''. Then QA should test it, ideally on all three platforms. If QA are happy with the result and the fix has been committed, QA move the bug status to '''RESOLVED - FIXED'''. That means the bug is closed. It will not be visible in searches except when searching for        [http://bugzilla.audacityteam.org/buglist.cgi?query_format=advanced&bug_status=RESOLVED&resolution=FIXED Fixed].
 +
 
 +
* It is suggested the only case where a developer should change bug status to '''RESOLVED - FIXED''' should be for bugs '''P3 and below''' where a logic error was to blame which does not appear to have possible platform or machine dependencies, and this fix has been committed.  
  
  

Revision as of 22:49, 23 July 2010

Audacity now tracks bugs and agreed enhancement issues on our Bugzilla. This page has links to Bugzilla queries listing bugs in different ways.


Quick Links:


Tip: For easy access, bookmark any links in these bug lists!


Latest Changes for:


Bugs by Priority

Open Bugs   Awaiting Developer Fix
PX   P1 only   P1 bugs prevent any release, including beta.
P1 to P2   P2 only P2 bugs prevent a stable release.
P1 to P3   P3 only P3 bugs must be release noted.
P1 to P4   P4 only P4 and P5 bugs are not release noted.
All Open Bugs   P5 only


Workflow when resolving bugs

  • The current workflow is that when a bug has a fix applied by a developer, the developer should move the bug status to DEVEL - FIX MADE. This means the bug is still OPEN. Then QA should test it, ideally on all three platforms. If QA are happy with the result and the fix has been committed, QA move the bug status to RESOLVED - FIXED. That means the bug is closed. It will not be visible in searches except when searching for Fixed.
  • It is suggested the only case where a developer should change bug status to RESOLVED - FIXED should be for bugs P3 and below where a logic error was to blame which does not appear to have possible platform or machine dependencies, and this fix has been committed.


Some Categories


Reports

Not strictly bug lists...

One Level

Two Levels

  • Bug Type and Priority. This is showing open bugs. It is possibly the best table for getting an overview of the kinds of live bugs we have.
  • Status and Priority. This is showing both open and closed bugs. It shows, for example, that we tend to close a higher proportion of high priority bugs than lower priority bugs.
  • Status and Bug Type. This is showing open and closed bugs. It shows, for example, that summary issues tend to stay open.

Three Levels