Re: What are the community's goals for 2.0? [was Re: Getting serious about releasing]

[Jim Gettys <Jim Gettys compaq com>]

Actually, the right criterion is:

"When the number of *NEW* bugs filed per week is significantly dropping,
you are ready to ship". (and you don't have show-stoppers left).

Doug Clark wrote several very nice papers on project management,
one of which was titled "Bugs are good".

As your user community grows, you get more and more duplicates
and therefore your total number of reports grows, even after fewer
new bugs are being found.

So understanding whether we're seeing fewer new bugs should go
into this equasion...

				- Jim


So I ask the question: what does the rate of *new* bugs look like.
> 
> I would say that we can judge the state of gnome2  by looking at the
> number of unique bug reports that are filed per week.  If there is a
> excessively high number then we're in bad shape.  (I'm not coding so I
> don't know what would count as excessive, individual maintainers would
> have to decide that)  We need to reflect and decide what works
> as a minimal functioning GNOME2.0 system.  For instance, I would
> throw out the menu editing stuff since it's currently broken as not
> necessary as part of the user experience.
> 


--
Jim Gettys
Cambridge Research Laboratory
Compaq Computer Corporation
Jim Gettys Compaq com

_______________________________________________
gnome-hackers mailing list
gnome-hackers gnome org
http://mail.gnome.org/mailman/listinfo/gnome-hackers