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.
-----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-----
On 04.08.2006, at 15:48, Patton, Eric wrote:
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.
Eric,
today I submitted two wishes via the form at [1] - I chose "type of report - wish" from the menu.
Both came through grass-devel classified as "bug".
Shouldn't the form be modified to classify them correctly as "wish" and consequently append them to their own queue of wishes instead of bugs?
\Flo.
[1]
http://grass.itc.it/bugtracking/bugreport.html
On Fri, Aug 04, 2006 at 09:26:47PM +0200, Florian Kindl wrote:
On 04.08.2006, at 15:48, Patton, Eric wrote:
>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.
Eric,
today I submitted two wishes via the form at [1] - I chose "type of
report - wish" from the menu.
Both came through grass-devel classified as "bug".
Shouldn't the form be modified to classify them correctly as "wish"
and consequently append them to their own queue of wishes instead of
bugs?
\Flo.
[1]
http://grass.itc.it/bugtracking/bugreport.html
In the HTML source code is used "wish6"
<td>
<select name="area">
<option value="grass6">bug in GRASS 6.0/6.1
<option value="wish6">wish for GRASS 6.1
<option value="doc-grass6">docs bug in GRASS 6
<option value="doc-wish-grass6">docs wish for GRASS 6
<option value="grass5.4">bug in GRASS 5.4
</select>
</td>
which should be ok. If it doesn't work I suspect something in the
bugtracker not functioning (any more).
?
Markus
On 05.08.2006, at 23:19, Markus Neteler wrote:
In the HTML source code is used "wish6"
<td>
<select name="area">
<option value="grass6">bug in GRASS 6.0/6.1
<option value="wish6">wish for GRASS 6.1
<option value="doc-grass6">docs bug in GRASS 6
<option value="doc-wish-grass6">docs wish for GRASS 6
<option value="grass5.4">bug in GRASS 5.4
</select>
</td>
which should be ok. If it doesn't work I suspect something in the
bugtracker not functioning (any more).
RT stores it in the "Area" wish6. So far, this is correct.
However, it is forwarded to grass-devel with Subject: [bug #nnnn]
^^^
?
\flo.