[GRASS-dev] GRASS at GForge first steps
bernhard at intevation.de
Tue Nov 7 05:13:57 EST 2006
On Tuesday 07 November 2006 05:57, Hamish wrote:
> > > > 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.
Often I have seen this used to turn down people.
> 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.
I follow Zeller pretty much here, but his writing goes into a lot more detail
of course. He just says that "bug" is quite general.
To me something that is "counter-intuitive" can be an issue
and a usuability problem.
Speaking of an "issue report" or "problem report" is a good general term,
because this does not judge to early what kind of problem the user or
Managing Director - Owner, www.intevation.net (Free Software Company)
Germany Coordinator, fsfeurope.org (Non-Profit Org for Free Software)
www.kolab-konsortium.com (Email/Groupware Solution, Professional Service)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
Url : http://lists.osgeo.org/pipermail/grass-dev/attachments/20061107/2aae23ab/attachment.bin
More information about the grass-dev