Chris (Sorry for not quoting that lengthy but very useful one.) I agree with you that it is very difficult to manage bug reporting in a way so that duplicates can be mostly avoided (as is with every system that processes mostly unstructured text entered by humans). Bugzilla certainly lacks a bit of functionality to achive that. I also do realize that developers put their reminders into bugzilla too and that "techincal" bug reports exist. But what I want to point out is that not individual figures matters but rather an impression, an overall feeling for the state of the project. And this is what disquiets me sometimes. It doesn't really matter what options/ parameters you choose for the bug chart. It always shows the same overall picture: bugs increase. On the other hand there is another really interesting chart: http://bugzilla.mozilla.org/reports.cgi?product=Browser&output=show_chart&datasets=RESOLVED%3A&links=1&banner=1
We can see now that you guys are not so slow at fixing bug as I thought originally. You fixed about 18'000 in the past half year already! Man, that is the hell of a lot! In this light the formerly posted figures may seem not so bad anymore. Beeing euphoric about developing the world's coolest, fastest, most reliable etc. best browser is ok. I mean you guys have done really good work so far (and some horrible as well of course). But do not lose the scope for details. All the small things that do not work correctly and behave strangely are more annoying to any user than a missing feature! I want to make you to set your priorities right. Ortwin Gl�ck
