Re: Bug#3253: Pine base64 bug
I think that we still need to separate the feature requests
from the bug reports, because they are *fundamentally* different, and
should probably have different action methodologies. Even if we do
not immediately treat them differently, we should leave the option
open by separating the two categories.
In some respects, the Bug tracking database *is* a database --
and not separating the bugs from feature requests violates the first
normal form. As you know, violating the first normal form makes it
harder to apply rules for one of the entity classes (like:-all *BUGS*
should be fixed within 9 months).
Separating bugs from feature requests shall leave people with
nothing to hide behind vis-avis fixing bugs -- and people with
feature requests shall not be reminded every week. I, for one, find
an open bug against my name an anathema.
a) Bug: The system does not work as intended or documented
b) Feature request: a request to enhance or modify the behaviour of
the product beyond the design and documentation
"In Germany they first came for the Communists, and I didn't speak up
because I wasn't a Communist. Then they came for the Jews, and I
didn't speak up because I wasn't a Jew. Then they came for the trade
unionists, and I didn't speak up because I wasn't a trade
unionist. Then they came for the Catholics, and I didn't speak up
because I was a Protestant. Then they came for me - and by that time
no one was left to speak up." Pastor Martin Niemoller
Manoj Srivastava <url:mailto:email@example.com>
Mobile, Alabama USA <url:http://www.datasync.com/%7Esrivasta/>
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
Trouble? e-mail to firstname.lastname@example.org .