Comment 8 for bug 90738
Revision history for this message
| Kim Nguyễn (kim.nguyen) wrote Re: Standard search fails to find bugs marked 'Fix released' | #8 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I hit this problem recently (as a ubuntu user):
There was a bug dubbed : "no sound hardy kernel 2.6.24-12" in the ubuntu project.
The bug didn't show up when searching for "no sound hardy" for instance.
This bug has many (52 as of today) duplicates. Half of them (26, as shown by their activity log) where reported after the fix was released (and to make things worse, many were commented on after they were marked as duplicates). This leads to increased email traffic (and noise) and extra work for the maintainers. It seems to be particularly a problem when nearing a release, when testing users are very active and fix are commited quickly. Further more, for big projects like Ubuntu, the fix usually takes some time to hit the mirrors. A solution could be to show "recently fixed" bugs, within a sensible time frame such as 2 or 3 days. However as pointed in a previous comment, this seems unnecessary for small projects or web based projects like launchpad itself since the fix is almost instantly applied. This should ultimately be a project-wise setting.