PEtALS 2.0 & pack (2007/09/28)| Chapter 8. Best practices | ||
|---|---|---|
 | ||
Table of Contents
When a bug is created; the category, summary and description fields must contain relevant information to unterderstand the bug. The GROUP field has to match the component version where the bug is found.
The PEtALS leader set the priority and affect a developer to the task. The correction starts here.
When the bug is corrected, the developer set the RESOLUTION field to FIXED. Moreover, he set the STATE field to PENDING.
When a release occurs for this component, the PEtALS leader set the STATE field to CLOSED and the version of the component is set as a comment.
When a feature is created; the category, summary and description fields must contain relevant information to unterderstand the feature. The GROUP field remains empty.
The Petals leader evaluates the request and, if accepted, sets a priority.
The Petals leader affects a developer to the task. The implementation starts here.
When the feature is implemented, the developer sets the STATE field to PENDING.
When a release occurs for this component, the PEtALS leader sets the STATE field to CLOSED and the GROUP field is set with the version where the feature can be found.
| | ||
| Chapter 7. Profiling with PEtALS |  |