Sometimes missing a core feature is a bug, and fixing a bug is adding a
feature (particularly if its making an existing feature more
~discoverable~).
So it might be necessary to establish an importance ~hierarchy~ for
bugs/features, to determine when something really overlaps both areas.
Smaller stuff might be more cut and dry of course, i.e., X is a feature
and Y is a bug. But there is some grey area too.
Just my 2 cents.
On 08/11/2011 11:55 AM, e-letter wrote:
Readers,
A recent feature request prompted the strategic question: what is more
important, minimising bugs or adding new features?
Of course, the ideal answer is to do both (;)), but remember, the
question is to choose only one answer...
--
Unsubscribe instructions: E-mail to [email protected]
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/discuss/
All messages sent to this list will be publicly archived and cannot be deleted
