Difference between revisions of "Bug Triage"

From ADempiere
Jump to: navigation, search
This Wiki is read-only for reference purposes to avoid broken links.
 
m (Where the bugs are)
Line 3: Line 3:
 
== Where the bugs are ==
 
== Where the bugs are ==
  
[[http://sourceforge.net/tracker/?atid=879332&group_id=176962&func=browse | SourceForge Bug Tracker]]
+
[http://sourceforge.net/tracker/?atid=879332&group_id=176962&func=browse | SourceForge Bug Tracker]
  
[[http://sourceforge.net/tracker/?atid=955896&group_id=176962&func=browse | SourceForge UI Tracker]]
+
[http://sourceforge.net/tracker/?atid=955896&group_id=176962&func=browse | SourceForge UI Tracker]
  
 
== How to Prioritize ==
 
== How to Prioritize ==

Revision as of 13:32, 28 November 2007

Here we document the meaning of the priority levels assigned to reported bugs.

Where the bugs are

| SourceForge Bug Tracker

| SourceForge UI Tracker

How to Prioritize

The Project Management Committee has established guidelines for using the priority field in the SF bug tracker. This was discussed in the PMC meeting of 03/06/2007, the notes are here: CC_Meeting_Full_20070306

If you are filling out a report, you can assign priority according to the following guidelines:

  • Priority 9 - system stopper - data corruption without workaround
  • Priority 7 - security issues
  • Priority 5 - not prioritized
  • Priority 3 - problems with workarounds - performance problems
  • Priority 1 - presentation problems

From time to time, the bugs will be triaged to re-prioritize them according to these standards.

Priority is important, because we will not announce a stable release while there are known priority 9 bugs.