Confirmed users
703
edits
SeaMonkey/QA/Triage HowTo: Difference between revisions
Jump to navigation
Jump to search
m
→Resolutions: DUPLICATE: oops
(→Triage: DUPLICATE (and DUPEME) -- new section) |
m (→Resolutions: DUPLICATE: oops) |
||
| Line 29: | Line 29: | ||
* [https://bugzilla.mozilla.org/describecomponents.cgi?product=NSS NSS] and [https://bugzilla.mozilla.org/describecomponents.cgi?product=NSPR NSPR] (these two change very little, only very few new bugs belong in them) | * [https://bugzilla.mozilla.org/describecomponents.cgi?product=NSS NSS] and [https://bugzilla.mozilla.org/describecomponents.cgi?product=NSPR NSPR] (these two change very little, only very few new bugs belong in them) | ||
==== Resolutions: DUPLICATE ==== | ==== Resolutions: DUPLICATE ==== | ||
* Can you find another bug for exactly the problem? Then one of them is a DUPLICATE of the other and should be RESOLVED as such. In general the older bug is left open and the newer one is closed as its DUPLICATE. The exception is when the newer bug is more detailed and contains more info which can lead to a solution: in that case, a comment should be added to the older bug explaining why it is resolved as a dupe of a newer bug. | * Can you find another bug for exactly the same problem? Then one of them is a DUPLICATE of the other and should be RESOLVED as such. In general the older bug is left open and the newer one is closed as its DUPLICATE. The exception is when the newer bug is more detailed and contains more info which can lead to a solution: in that case, a comment should be added to the older bug explaining why it is resolved as a dupe of a newer bug. | ||
* Can you remember seeing another case of the same bug in the recent past, without being able to find it back now? In that case you may add DUPEME to the Whiteboard, but only if you are '''positive''' that you saw another bug for the same problem. | * Can you remember seeing another case of the same bug in the recent past, without being able to find it back now? In that case you may add DUPEME to the Whiteboard, but only if you are '''positive''' that you saw another bug for the same problem. | ||
==== Resolutions: INCOMPLETE and WORKSFORME (and NEEDINFO flag) ==== | ==== Resolutions: INCOMPLETE and WORKSFORME (and NEEDINFO flag) ==== | ||
Is the bug '''still found''' in current SeaMonkey versions (latest release, latest beta, latest Aurora nightly, latest comm-central-trunk nightly)? If you can't decide, add a comment to the bug asking the reporter, and in that case click the NEEDINFO checkbox at the bottom of the bug page, set the info provider to "reporter" in the rolldown, and also add [CLOSEME yyyy-mm-dd INCO] or [CLOSEME yyyy-mm-dd WFM] (where yyyy-mm-dd is a "reasonably" future date) to the Whiteboard. | Is the bug '''still found''' in current SeaMonkey versions (latest release, latest beta, latest Aurora nightly, latest comm-central-trunk nightly)? If you can't decide, add a comment to the bug asking the reporter, and in that case click the NEEDINFO checkbox at the bottom of the bug page, set the info provider to "reporter" in the rolldown, and also add [CLOSEME yyyy-mm-dd INCO] or [CLOSEME yyyy-mm-dd WFM] (where yyyy-mm-dd is a "reasonably" future date) to the Whiteboard. | ||