> If you want to know what 1.0 is going to be, all you need to do is look at the > requirements specifications for the product and its compomnents, which should > spell it all out. We have those? :-) > As for bugs, historical bug > fix rates can be applied to the number of open bugs (bugs which, if not fixed, > mean we can't meet the goals spelled out in the requirements specifications), > and a projected incoming rate, to determine about how long (roughly) it will > take to fix the problems (modulo time for testing, vacations, attrition, etc.) If you consult the bug charts, you will notice that bugs are incoming faster than they are being fixed, by a reasonable margin. I therefore hope that this calculation won't be the way to decide how close 1.0 is :-) Gerv
- Re: Towards Mozilla 1.0 Ian Hickson
- Re: Towards Mozilla 1.0 Bernd Mielke
- Re: Towards Mozilla 1.0 Andreas Franke
- Re: Towards Mozilla 1.0 Ian Hickson
- Re: Towards Mozilla 1.0 John Dobbins
- Re: Towards Mozilla 1.0 Josh Soref
- Re: Towards Mozilla 1.0 Christopher Blizzard
- Re: Towards Mozilla 1.0 Syd Logan
- Re: Towards Mozilla 1.0 Bernd Mielke
- Re: Towards Mozilla 1.0 Andreas Franke
- Re: Towards Mozilla 1.0 Gervase Markham
- Re: Towards Mozilla 1.0 Tim McNerney
- Re: Towards Mozilla 1.0 Josh Soref
- Re: Towards Mozilla 1.0 Fabian Guisset
- Re: Towards Mozilla 1.0 Randall Parker
- Re: Towards Mozilla 1.0 Josh Soref
- Re: Towards Mozilla 1.0 RV
- Re: Towards Mozilla 1.0 Randall Parker
- Re: Towards Mozilla 1.0 DeMoN_LaG
- Re: Towards Mozilla 1.0 Randall Parker
- Re: Towards Mozilla 1.0 Randall Parker
