[GRASS-dev] GRASS at GForge first steps

Hamish hamish_nospam at yahoo.com
Mon Nov 6 23:57:51 EST 2006

> > > how is a defect different than a bug?

> > Call it "bad feature". I sometimes was told that I was reporting
> > something as a bug while actually it was a feature. Although that
> > feature was not good - eg. the current memory overhaed in GRASS
> > vectors and dbf driver. Do you want a separate tracker for defects
> > and bugs (I'd prefer them kept in one tracker, so that defects are
> > as attended as bugs are).

> I think a bug is also too general as a term. Zeller 2006 explains
> this and uses "defect".
> See http://www.whyprogramsfail.com/

FWIW, Debian has a "wontfix" tag for bugs.

I think to say all features which do something other than what a user
might expect at first are "misfeatures" or a "defect" is wrong. Some are
real defects/shortcomings, but others are counter-intuitive yet correct
design choices.



More information about the grass-dev mailing list