If it seems that a bug should be reclassed as a wish, I include a note in
the BT saying why I think so, CC'ing it to Maciek. If he's in agreement, he
takes care of it.
~ Eric.
-----Original Message-----
From: Paolo Cavallini
To: Patton, Eric
Cc: 'grass-dev@grass.itc.it'
Sent: 8/4/2006 9:51 AM
Subject: Re: [GRASS-dev] Bugs vs. wishes
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Right. Could you reclassify the bugs as wishes?
All the best.
pc
Patton, Eric ha scritto:
Hi guys,
One thing that I've noticed a lot in the brief time I've been pouring
through old bugs is how often a wish is submitted as a bug. Ideas for
improvments, complaints about 'this could be better' or 'it should
work this
way instead' get submitted as bugs when they are /not/ bugs. If
software
doesn't work the way you think it should, this is not a bug. It is a
wish. I
find that a lot on the BT.
I wonder if there is a way to put some kind of message in bold letters
on
the BT advising the user to clearly discriminate between what they
want the
software to do (a wish) vs. what it is supposed to do based on the
Grass
documentation (a bug). A /lot/ of "bugs" could be prevented this way.
It's
fine to have a wish list a mile long, but the more we can prevent
false bugs
from being posted, the faster we can get a true bug short list created
for
the devs.
I don't know if there is anything that can really be done about it,
I'm just
grumbling. (I'll submit a wish for this).
~ Eric.
--
Paolo Cavallini
email+jabber: cavallini@faunalia.it
www.faunalia.it
Piazza Garibaldi 5 - 56025 Pontedera (PI), Italy Tel: (+39)348-3801953
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFE01D6/NedwLUzIr4RAtT3AJ4o9jTEs06PdzPvDuKgXB46ICm5UQCdHtnU
+iJma4xgHlirfijL0DqET4k=
=mcU0
-----END PGP SIGNATURE-----