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.
   −
'''WORKSFORME''' The bug can not be reproduced.
+
== Severity (Default=Unspecified) ==
 
  −
 
  −
== Severity (Default=Normal) ==
   
This field describes the impact of a bug on a user.
 
This field describes the impact of a bug on a user.
   Line 46: 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 52: 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 64: 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 72: Line 69:  
'''Enhancement''' Request for a new feature or functionality.
 
'''Enhancement''' Request for a new feature or functionality.
   −
== Sugar Version ==
+
== Sugar Version (Default=Unspecified) ==
 
This field describes the version of Sugar that a bug has most recently been found in. This field is used by the Sugar release team and other  
 
This field describes the version of Sugar that a bug has most recently been found in. This field is used by the Sugar release team and other  
 
interested parties to find all bugs in a specific version of Sugar, no matter what program the bug is in. For example, one query can find all Sugar 0.82 bugs, whether they are in sugar-toolkit 0.82.1, browse 100, or sugar-artwork 0.82.
 
interested parties to find all bugs in a specific version of Sugar, no matter what program the bug is in. For example, one query can find all Sugar 0.82 bugs, whether they are in sugar-toolkit 0.82.1, browse 100, or sugar-artwork 0.82.
Line 79: Line 76:  
updating the product version field - that is still useful for maintainers.
 
updating the product version field - that is still useful for maintainers.
   −
'''Unspecified''' (Default) This bug is in a module that is not in Sugar, or in an unspecified version of Sugar.
+
'''Unspecified''' This bug is in a module that is not in Sugar, or in an unspecified version of Sugar.
    
'''Git as of bug date''' In the recent version from git
 
'''Git as of bug date''' In the recent version from git
Line 87: Line 84:  
'''0.82.x''' Stable release
 
'''0.82.x''' Stable release
   −
== Component Target Milestone ==
+
== Component Target Milestone (Maintainers Field) ==
 
This field describes the version of the product that developers or the maintainers believe they should fix the bug by. This field is not meant for use by general users, the BugSquad, or the release team. It is reserved for developers and maintainers of the given module.
 
This field describes the version of the product that developers or the maintainers believe they should fix the bug by. This field is not meant for use by general users, the BugSquad, or the release team. It is reserved for developers and maintainers of the given module.
   Line 93: Line 90:  
This field describes the version of Sugar that a bug should be fixed in. This is not a 'it would be nice' field, it is a 'Sugar releases may need to be delayed for this issue' field. It is intended for use by senior-ish bug triagers and the release team. We allow others to nominate 'showstopper' bugs by setting this field, but bugsquadders and release team members review such bugs and unmark ones where the change is not warranted.
 
This field describes the version of Sugar that a bug should be fixed in. This is not a 'it would be nice' field, it is a 'Sugar releases may need to be delayed for this issue' field. It is intended for use by senior-ish bug triagers and the release team. We allow others to nominate 'showstopper' bugs by setting this field, but bugsquadders and release team members review such bugs and unmark ones where the change is not warranted.
   −
== Operating System ==
+
Default: Unspecified by Release Team
This field lists the operating system (distribution) the bug was found on. Debian, Fedora, OLPC...
+
 
 +
== Distribution/OS ==
 +
This field lists the Sugar distribution (operating system) the bug was found on. Fields: Debian, Ubuntu, Fedora, OLPC, Gentoo...
 +
 
 +
[[Category:BugSquad]]

Navigation menu