Bug symptoms are often vaguely specified as the reporter is unfamiliar with the problem, for example sound not working, there can be any number of causes for these kinds of symptoms and it is critically important that the information we collect for any one issue is specific to the issue the reporter is seeing. Even minor revisions of the same hardware can mean that apparently similar bugs have different root causes.

There are two ways to handle these cases:

  1. use a common bug until we determine we have two (or more) issues and then split the original report
  2. use separate bugs for each issue and then merge the bugs into one once we are certain they are the same

The first is very tricky to manage as we have to unpick the already merged information from the many reporters and there is no way to strip the now unrelated commentary from the original bug. The second leads to an initial increase in bugs but the individual reporters and their data is clearly separated.

In order to resolve this issue the Ubuntu Kernel Team recently adopted a No Duplicates policy with regard to bugs. This means that bugs only will be duplicated once a kernel developer has confirmed the issue is identical and no value is being added by maintaining multiple bugs. Note that even there, the original separation of reported system information is still maintained and has value.

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)