[GRASS-dev] GRASS at GForge first steps

Bernhard Reiter bernhard at intevation.de
Mon Nov 6 09:27:51 EST 2006

On Sunday 05 November 2006 10:57, Maciej Sieczka 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/ 

> > While we commision the new tracker(s), I would like to see the old bug
> > tracker kept alive for some time, even if less used.
> This was already agreed on the dev list IIRC. Old GRASS RT is going to
> be used for the old bugs, since nobody seems to be able to transfer
> them to GForge.

It is a matter of effort and time, but not technically impossible. :)

> New bugs will be reported at GForge - not yet though, 
> GRASS' GForge is still at development stage :) - give some more time.

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
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.osgeo.org/pipermail/grass-dev/attachments/20061106/ff20f5e7/attachment.bin

More information about the grass-dev mailing list