Difference between revisions of "Bug Triage"
From ADempiere
This Wiki is read-only for reference purposes to avoid broken links.
(→Priority) |
(→How to Prioritize) |
||
Line 6: | Line 6: | ||
[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] | ||
+ | |||
+ | == Helping with Triage == | ||
+ | # Anyone can help. It is a matter of looking at bug reports, trying to reproduce in the daily build, then setting the priority of the bug. | ||
+ | # Get the latest code/db. | ||
+ | * use the ready-to-run NX client at [www.testadempiere.com testadempiere.com] (hosted by [www.idalica.com Idalica]) | ||
+ | * download the daily adempiere binary from [www.testadempiere.com testadempiere.com] | ||
+ | * download and build the sources yourself, and apply all the latest migration scripts. | ||
+ | # If you can reproduce the bug in the latest build, set the priorities as noted below. | ||
+ | # If there is not enough information to reproduce, then you can ask for more details. | ||
+ | # If you can not reproduce the error, then close the bug, and say 'Works in latest version' ;) | ||
+ | |||
== How to Prioritize == | == How to Prioritize == |
Revision as of 13:33, 9 December 2007
Here we document the meaning of the priority levels assigned to reported bugs.
Contents
Where the bugs are
Helping with Triage
- Anyone can help. It is a matter of looking at bug reports, trying to reproduce in the daily build, then setting the priority of the bug.
- Get the latest code/db.
- use the ready-to-run NX client at [www.testadempiere.com testadempiere.com] (hosted by [www.idalica.com Idalica])
- download the daily adempiere binary from [www.testadempiere.com testadempiere.com]
- download and build the sources yourself, and apply all the latest migration scripts.
- If you can reproduce the bug in the latest build, set the priorities as noted below.
- If there is not enough information to reproduce, then you can ask for more details.
- If you can not reproduce the error, then close the bug, and say 'Works in latest version' ;)
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 and group according to the following guidelines:
Resolution
- Remind - In some cases, there is already a patch or code snippet in the bug report that has not yet been applied. In these cases, set the Resolution to "Remind" and these can be looked at first on a bug day.
Priority
- 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
Group
It's very important also to assign the group for the bug:
- Beta - if you're reporting a bug over a beta functionality
- Core - if you're reporting a bug over a core functionality
- Module specific - if you're reporting affecting just a specific module (not core)
- Report - if you're reporting problems of presentation or reports
Release
From time to time, the bugs will be triaged to re-prioritize them according to these standards.
Priority and group are important, because we will not announce a stable release while there are known priority 9 bugs on core.