The Eclipse Project uses the following values for the bugzilla Product field:
The 'Target Milestone' field lists the Milestone or Release in which a bug is intended to get fixed or was first fixed. The fix can be assumed to be present in all milestones or releases after that point, unless otherwise specified in the bug. The notation used is as follows:
- x.y.z - indicates a final release build in which the fix/enhancement was made
- x.y.z M# - indicates a milestone build in which the fix/enhancement was made
- x.y.z RC# - indicates a release candidate build in which the fix/enhancement was made
- 2.0 F# - indicates a release candidate build from the 2.0 release. The term freeze was replaced with release candidate in subsequent releases
- x.y.z+ - indicates the fix was made after the x.y.z release, and was released into the Rx_y_maintenance branch in CVS corresponding to that release. If a hypothetical x.y.(z+1) release were to occur, it would contain the release, but no such release is scheduled. For example 3.4.2+ indicates the fix was released in the R3_4_maintenance branch in CVS sometime after the 3.4.2 release, and would be included in a theoretical 3.4.3 release if such a release occurred.
Priority is set by the committer or contributor that the bug is assigned to, or by the component owner. This roughly indicates the importance of the bug/enhancement relative to the other bugs/enhancements owned by the committer or component.
|| Must fix for the indicated target milestone. Literally. We will slip dates for P1's, so use sparingly.|
|| Very important for the indicated target milestone. Nearly all P2's should be resolved, so do not over use.|
|| Of normal importance. Default starting point. While triaging a bug it is good to consider its priority and adjust higher or lower if appropriate. |
||Less important. Would like to fix the bug, time permitting.|
|| A valid bug, but no plans to investigate further or fix. All P5 bugs also imply 'helpwanted', but 'helpwanted' can also be used on any other priority. |
Severity is set by the person who reported the bug. The bug owner can change the severity or request the originator do so if their description of the problem is inconsistent with the definition of the severity. However, the severity represents the originator's perspective and should not be changed by others purely because they have a different perspective. For example if the originator only uses Eclipse for spell-checking, and the spell-checking function is not working, they can fairly say the bug is blocking even though from the committer's perspective it is only a major problem.
|| Blocks development and/or testing work. No workaround exists.|
|| Crashes, loss of data, severe memory leak.|
|| Major loss of function.|
|| Regular issue, some loss of functionality under specific circumstances.|
|| Minor loss of function, or other problem where easy workaround is present.|
|| Cosmetic problem such as misspelled words or misaligned text.|
|| Request for enhancement.|
Tracking IP Contributions
IP contributions are tracked in bugzilla using the "iplog" flag. The "iplog" flag should be set on the *attachment* that contains the contribution. This is done by clicking "Details" next to the attachment, and then setting the "iplog" flag for that attachment. If there are multiple attachments being contributed, add the flag for each applicable attachment. This allows the system to automatically harvest data about the size of the contribution, who contributed it (the person who added the attachment), and the committer who processed the contribution (the person who set the "iplog+" flag).
Note: it doesn't matter if the attachment from the contributor is obsolete. If you have taken a contribution from someone, and made a few small changes and attached a new patch, you should still flag the obsolete patch with iplog+ to record the contribution that the fix was based on.
There is also an "iplog" flag for the entire bug report next to the "review" and "pmc_approved" flags. This flag should only be used if the contribution is not in the form of an attachment. For example, you can use this if the contributor added code or pseudo-code directly in the comment field. The simple solution in this case is to ask the contributor to attach a proper patch so it can be flagged. If this is not possible or the contributor doesn't respond, you can resort to setting the global "iplog" flag on the bug itself. What this flag does is flag every non-committer who added a comment to the bug as contributors. If there are comments in the same bug that are not part of the contribution, they then need to be excluded manually by editing the project IP log. This is a painful process, so using attachments to track contributions is always preferred if possible. See the IP log documentation for more details: Development_Resources/Automatic_IP_Log#Contributors
Common, routine, Team Bugzilla queries
Open bugs per milestone target
These queries are especially handy as we near the end of a release, or milestone -- to see what still needs to be triaged.
Its best to review these to make sure nothing would be holding up a release. Blockers, especially, should have some amount of triage before a release, such as if not able to reproduce, then there should be comment saying that. Or, if can reproduce, but can not fix before a release, then a statement on what the plan is to fix it.
It is also good to triage these from time to time, and make sure they are classified correctly.
- All "Blocker" or "Critical" bugs