Ortwin Gl�ck wrote:
> Looking at the bug statistics at
>
>
>http://bugzilla.mozilla.org/reports.cgi?product=-All-&output=show_chart&datasets=NEW%3A&datasets=ASSIGNED%3A&datasets=REOPENED%3A&datasets=UNCONFIRMED%3A&links=1&banner=1
>
>
> Bugs are taking over!
>
> Fact:
> The number of bugs is now three times as high as half a year ago: over
> 12,000 open bugs!
>
> Are Mozilla developers creating more bugs than they (can ever) fix?
No. It is the bug reporters.
> Where is this going to end?
> Do you guys actually write unit tests? I doubt it. There are so many
> bugs that are just broken features that have worked before.
The only problem which I see with the ever increasing number of bugs
is longer search times on Bugzilla. Everything else gets better.
> If I were a Mozilla project manager I would suggest:
>
> - stop new features
> - have all the code reviewed
> - write unit tests
> - perform regression tests regularly
> - refine the check-in process (unit/regression test before checking in)
> - refactor where necessary
> - fix bugs
> - take your time: it's ready when it's ready
> - when the number of bugs is back to a normal level: rewrite project plans.
- close Bugzilla, so that no new bugs are submitted.
RB
