![]() No workaround exists.Ĭrashes, loss of data, severe memory leak. 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.īlocks development and/or testing work. However, the severity represents the originator's perspective and should not be changed by others purely because they have a different perspective. 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. Severity is set by the person who reported the bug. All P5 bugs also imply 'helpwanted', but 'helpwanted' can also be used on any other priority. Would like to fix the bug, time permitting.Ī valid bug, but no plans to investigate further or fix. While triaging a bug it is good to consider its priority and adjust higher or lower if appropriate. Nearly all P2's should be resolved, so do not over use. ![]() Very important for the indicated target milestone. We will slip dates for P1's, so use sparingly. Must fix for the indicated target milestone. This roughly indicates the importance of the bug/enhancement relative to the other bugs/enhancements owned by the committer or component. Priority is set by the committer or contributor that the bug is assigned to, or by the component owner. If a bug is fixed during M2 time frame and the bug is triaged to x.y M3 milestone, it is recommended to put x.y M2 ( please note a space before M2) in Whiteboard section for easier trackability.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. If a hypothetical x.y.(z+1) release were to occur, it would contain the release, but no such release is scheduled. 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.The term freeze was replaced with release candidate in subsequent releases 2.0 F# - indicates a release candidate build from the 2.0 release.x.y.z RC# - indicates a release candidate 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 - indicates a final release build in which the fix/enhancement was made.The fix can be assumed to be present in all milestones or releases after that point, unless otherwise specified in the bug. The 'Target Milestone' field lists the Milestone or Release in which a bug is intended to get fixed or was first fixed. The Eclipse Project uses the following values for the bugzilla Product field: This page provides details on how the Eclipse project uses bugzilla. The Eclipse Project uses Eclipse Bugzilla for bug tracking. 4 Common, routine, Team Bugzilla queries.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |