>    I'm not sure I completely understand this.  If more work is being
> done on crashers, etc. then there will end up being less (tending
> towards, hopefully, 0) of them.  The fewer number of crashers, the
> GREATER amount of time that people will have to work on non-crash
> related bugs.  Some comments on this thinking:

If we get to the wonderful position of having no crash bugs, we do not
then land a whole slew of new features, however voted for they are. We
keep the stability and work towards shipping.
 
> 2. Isn't there something wrong with the process when crashers and
> dataloss bugs aren't ALWAYS the first priority in development?  Why

No. For example, we left crashers in the old imglib for months because we
were rewriting it.

Gerv



Reply via email to