DuplicateBugs
|
Size: 1107
Comment:
|
Size: 1733
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 4: | Line 4: |
This is due to the use of slightly different, or minor revisions to, chip sets in otherwise identical hardware. This causes slightly different behavior across apparently identical hardware. From experience, fixes that should have resolved a reported issue generally leave several reporters in the same state as they reported previously. In these cases, if the similarly affected person opted to identify a bug as affecting them instead of filing a new and separate bug for the issue, there will have been no environment or logging information gathered for this new reporter. The person not solved by the fix would then be required to open a new bug for their issue. The team prefers to treat systems as separate unique hardware and discourage the duplication of bugs in order to address this while gathering all necessary logging at the time of the bug being filed. |
This is an effort to eliminate 'conflated' bugs, or bugs that have been inundated by 'me too' comments or comments from anyone other than the original bug reporter indicating that they see the same issue on <other hardware or chipset>. In most cases this has the unfortunate side-effect of taking the focus from the original report and making the focus of the bug on some specific symptom that may not have been the cause of the bug report in the first place. The kernel team refer to these bugs as 'hijacked' reports. In most cases this is not intentional, however, this policy is meant to address the issue. Another added benefit of putting a policy, such as this, in place is the simplification of issues encountered with slightly different, or minor revisions, to chip sets in otherwise identical hardware. From experience, fixes that should have resolved a reported issue generally leave several reporters in the same state as they reported previously. In these cases, if the similarly affected person opted to identify a bug as affecting them instead of filing a new and separate bug for the issue, there will have been no environment or logging information gathered for this new reporter. The person not solved by the fix would then be required to open a new bug for their issue. The team prefers to treat systems as separate unique hardware and discourage the duplication of bugs in order to address this while gathering all necessary logging at the time of the bug being filed. |
The Ubuntu Kernel Team recently adopted a No Duplicates policy with regard to bugs.
This is an effort to eliminate 'conflated' bugs, or bugs that have been inundated by 'me too' comments or comments from anyone other than the original bug reporter indicating that they see the same issue on <other hardware or chipset>. In most cases this has the unfortunate side-effect of taking the focus from the original report and making the focus of the bug on some specific symptom that may not have been the cause of the bug report in the first place. The kernel team refer to these bugs as 'hijacked' reports. In most cases this is not intentional, however, this policy is meant to address the issue.
Another added benefit of putting a policy, such as this, in place is the simplification of issues encountered with slightly different, or minor revisions, to chip sets in otherwise identical hardware. From experience, fixes that should have resolved a reported issue generally leave several reporters in the same state as they reported previously. In these cases, if the similarly affected person opted to identify a bug as affecting them instead of filing a new and separate bug for the issue, there will have been no environment or logging information gathered for this new reporter. The person not solved by the fix would then be required to open a new bug for their issue. The team prefers to treat systems as separate unique hardware and discourage the duplication of bugs in order to address this while gathering all necessary logging at the time of the bug being filed.
This policy supersedes generally practiced Ubuntu Bug Triage guidelines for the kernel and it's associated packages.
Kernel/Policies/DuplicateBugs (last edited 2010-07-21 10:34:06 by 193)