There is a new Bugzilla report, intended to replace the most-frequent-bugs
list, at
http://bugzilla.mozilla.org/duplicates.cgi .
You can get "Most recently duplicated bugs" by doing:
http://bugzilla.mozilla.org/duplicates.cgi?sortby=bug_no
Both of these reports are linked from the front page of b.m.o, and will be
linked from other placed later.
A few words about how this works:
1) It shows RESOLVED but not VERIFIED bugs. This means two things.
- people need to go through the currently-displayed list and VERIFY
those which were closed a while ago, to make the list more useful
- if a bug is a known mostfreq, and gets RESOLVED, we should hold off
from VERIFYing it for a few days to keep it on the list, so that fewer
dupes get filed by people using old builds.
2) We need to do better summaries.
The only description people get of bugs is the Summary. In the past, I
sometimes invent new summaries for the mostfreq list if the summary is
something like "Crash in Trunk [@ nsWalletlibService::OnStateChange]".
However, this will no longer be possible, so summaries need to describe
symptoms, and the fact that the crash is in OnStateChange can safely be
left in a comment. If you see a bug on the list with a silly summary, fix
it.
3) We need to do better components.
The same above applies for Components. I know some of our component names
are a bit obscure - this is why a good summary is important - but we
should avoid leaving bugs in Browser-General if "they are going to be
fixed quickly" or anything like that.
Comments and improvement ideas welcome.
Gerv
