MozillaZine

Mozilla 0.9.3 Released!

Thursday August 2nd, 2001

mozilla.org today released Mozilla milestone 0.9.3, continuing to work towards a 1.0 release. Preliminary data is showing that 0.9.3 is up to 35% more stable than 0.9.2, thanks to increased focus on stability bugs this milestone. Along with that, the newest incarnation of the Modern has had some additional work since 0.9.2.

Builds are available on mozilla.org's download page (or go right to the FTP directory), along with release notes.


#31 Some concerns about bug trend ...

by bcwright <bcwright@ix.netcom.com>

Friday August 3rd, 2001 11:53 AM

You are replying to this message

There are some concerns about the recent trend in the bug count however. Without more extensive analysis it's difficult to get a good feel for what the raw numbers mean, but the number of open entries that are marked "blocker", "critical", or "major" that are targetted to be fixed for 0.9.3 through 1.0 has slowly risen over the last month from about 500 to (currently) about 539.

There are several possible explanations for this:

1) More bugs have been identified that were always there.

2) More enhancement requests in those classes have been added for inclusion in 1.0.

3) There have been a lot of regressions over the last month.

4) Some of the bugs may have been split into two or more component bugs in order to better reflect the underlying issues.

5) Some bugs may have been upgraded from less severe categories into the more severe categories.

Only choice #3 indicates that there may be a problem with declining code quality; choice #2 may mean that the "second system" management problem is starting to add bells and whistles for inclusion faster than they can be written (a worrisome issue since it potentially can make the march to 1.0 stretch out into an arbitrarily long time). The other possibilities are basically administrative, but _may_ indicate that the original target was more ambitious than originally thought and may take longer to achieve.

If the project is to achieve closure on 1.0 then it will be necessary to get a handle on this. What would be required to do so depends a great deal on why the list is growing faster than bugs on it are being retired (and a lot of them are being retired, as can be easily verified).

Does anyone who has more familiarity with the open bug list than I do have any comments on this (asa)?

Bruce