Bugzilla Guidelines for RAP Committers
- when triaging bugs:
- set status to assigned if the bugs appears valid
- set priority if needed (see section below)
- when start working on a bug
- assign it to yourself
- copy others that might be interested
- when stop working on a bug
- reassign to inbox to broadcast subsequent changes
- when closing a bug
- reassign to inbox before closing to broadcast the change
- shortly describe the problem/solution
- set target milestone for fixed bugs
We use priorities as follows:
- P1: Critical. Should be fixed within the current milestone.
- P2: Release critical. Should be fixed before the release.
- P3: Normal bug (default).
- P5: It's a valid bug, but will not fix it in the foreseeable future.
RAP uses the 'Status Whiteboard' field to label bugs with:
- srNNN used for tagging bugs that are fixed in the maintenance branch of the last release. See Backporting fixes for service releases
- srNNN? used for tagging bugs should be backported to the maintenance branch of the last release. See Backporting fixes for service releases
qx-openobsolete. Has been used for bugs that depend on an unresolved qooxdoo bug. The bug id of the qooxdoo bug should be found in one of the comments. qx-closed: obsolete. Has been used once a blocking qooxdoo bug was resolved (see qx-open). This way, all unresolved RAP bugs could be identified that should be solved after migrating to the next qooxdoo service release. extend-rwtobsolete. Has been used only for the 1.2 plan. All bugs labeled that way will be shown in the Reduce the gap between RWT and SWT theme.
Please refer to the description of Keywords used in Eclipse Bugzilla.
Status and Resolution
Please read this document for a list of statuses and their use.