Changes

Jump to navigation Jump to search
m
Line 1: Line 1: −
Inspired by the [http://bugzilla.gnome.org/page.cgi?id=bug-status.html bug status fields from gnome] I would do the following:
+
{{TOCright}}
 
+
== Bug Status (Default=Unconfirmed)==
 
  −
== Bug Status ==
   
The status field indicates the general status of a bug. What state we are in the life cycle of a bug?
 
The status field indicates the general status of a bug. What state we are in the life cycle of a bug?
   Line 34: Line 32:  
'''DUPLICATE''' This bug is filed already in the data base.
 
'''DUPLICATE''' This bug is filed already in the data base.
   −
== Severity (Default=Normal) ==
+
== Severity (Default=Unspecified) ==
 
This field describes the impact of a bug on a user.
 
This field describes the impact of a bug on a user.
   Line 43: Line 41:  
'''Major''' Major loss of functionality - menu item broken, data output extremely incorrect, or otherwise difficult/useless to use
 
'''Major''' Major loss of functionality - menu item broken, data output extremely incorrect, or otherwise difficult/useless to use
   −
'''Unspecified''' A minor part of the component is non functional or broken
+
'''Unspecified'''
    
'''Minor''' minor loss of function, or other problem where easy workaround is present.
 
'''Minor''' minor loss of function, or other problem where easy workaround is present.
Line 49: Line 47:  
'''Trivial''' Cosmetic problem like misspelled words or misaligned text.
 
'''Trivial''' Cosmetic problem like misspelled words or misaligned text.
   −
== Priority (Maintainers field) ==
+
== Priority (Maintainers field, Default=Unspecified by Maintainer) ==
This field describes the importance and order in which a bug should be fixed. This field is ''utilized by hackers'' to prioritize their work to be done. While each term has a description, it is important to note that priority is highly subjective, and bugs can move up or down the priority scale based on subjective questions like 'would we be embarassed to release the software with this bug.'
+
This field describes the importance and order in which a bug should be fixed. This field is ''utilized by hackers'' to prioritize their work to be done. While each term has a description, it is important to note that priority is highly subjective, and bugs can move up or down the priority scale based on subjective questions like 'would we be embarrassed to release the software with this bug.'
    
'''Immediate''' This bug blocks development or testing work and should be fixed ASAP, or is a security issue in a released version of the software.
 
'''Immediate''' This bug blocks development or testing work and should be fixed ASAP, or is a security issue in a released version of the software.
Line 61: Line 59:     
'''Low''' Just not all that important. Rarely used in Sugar.
 
'''Low''' Just not all that important. Rarely used in Sugar.
 +
 +
'''Unspecified by Maintainer''' This is a field for the maintainer only.
    
== Type (Default=Defect) ==
 
== Type (Default=Defect) ==
Line 92: Line 92:  
Default: Unspecified by Release Team
 
Default: Unspecified by Release Team
   −
== Operating System ==
+
== Distribution/OS ==
This field lists the operating system (distribution) the bug was found on. Debian, Fedora, OLPC...
+
This field lists the Sugar distribution (operating system) the bug was found on. Fields: Debian, Ubuntu, Fedora, OLPC, Gentoo...
 +
 
 +
[[Category:BugSquad]]

Navigation menu