Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index

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:

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
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.