PLEASE READ (at least) THIS: I wanted to learn from NetBeans 3.2 stabilization
and try to predict how NB3.3 stabilization will be going. The first table shows numbers of bugs
during NB3.2 stabilization and the second table shows our current bugs statistics (7/13-8/17).
The numbers are not representing the same (NB3.2 counts only bugs reported for NB3.2 branch,
but NB3.3 table counts all opened bugs).
1. NetBeans 3.2 Stabilization
The first table shows the stabilization of NetBeans 3.2. Before stabilization
we had 592 bugs and when we released we had about 372 bugs. We resolved about
1300 bugs but discovered about 1150 new. According to Honza Chalupa not all
bugs were included in this counts (because were reported for different branch).
So the numbers do not represent total number of opened bugs during stabilization.
This table shows the numbers of bugs during last couple of weeks. Last date
is 8/17 that is 2 weeks before NB3.3 feature freeze (=stabilization start).
The numbers during last week started to be alarming. We have currently
1069 all opened bugs. Some weeks don't look good (e.g. +140 - 83
bugs! during last week)
NetBeans 3.2 and NetBeans 3.3 are different. Different schedule,
different features, etc. It is not so simple, just compare the numbers
It the NB3.2 table there are not all bugs involved (so
the total opened bugs numbers could be +200 or something like that). NetBeans
3.3 numbers represent all currently opened bugs numbers.
It seems that:
We are able to resolve up to 150-200 bugsevery week.
A lot of new bugs were discovered during NB 3.2 stabilization:
1300 resolved vs. 1150 new.
It will probably be the same for NB3.3.
Sun's QA spent more or the same time on NB3.2 compared
to NB3.3 during implementation phase (before feature freeze). So, we
can't say that for NB3.3 we have more bugs discovered in advance - before