[GNC-dev] Bugzilla Keywords -- keep or drop (and which ones)?

John Ralls jralls at ceridwen.us
Mon May 14 14:16:53 EDT 2018

> On May 14, 2018, at 10:11 AM, Frank H. Ellenberger <frank.h.ellenberger at gmail.com> wrote:
> Am 14.05.2018 um 18:10 schrieb Derek Atkins:
>> Hi,
>> On Mon, May 14, 2018 11:41 am, John Ralls wrote:
>>> The existing keywords don’t seem terribly useful to me and they’re in any
>>> case not used consistently enough: only 364 out of 8590 GnuCash bugs have
>>> a keyword on them. I don’t think that there’s any need to import them
>>> unless BZ requires it.
> Some are only useful, for a QA with a team like that of gnome. Others
> were much more useful, if we would apply them more consistently.
> Example: "Documentation" should be set already, if something has to be
> fixed in engine first, but also needs documentation. Then after engine
> is fixed, it should not be closed as fixed. Instead it should be
> reassigned to documentation.
> So which we should drop, we should decide in a later step.

The keywords in use on GnuCash bugs are:
accessibility (9)
API (6)
build (3)
documentation (36)
I18N (19)
HIG (2)
keynav (5)
L10N (10)
memory (2)
newcomers (6)
perf (4)
portability (1)
pref (10)
printing (1)
qa (1)
relate (1)
security (3)
string (4)
usability (239)

A spot check shows they seem  mostly to be added at bug creation time by bug reporters, few of whom are likely to be able to make an informed choice. But as you say it's more important to get BZ up and running, and we may yet decide to switch to a different tracker which would make it moot. We can worry about this later.

John Ralls

More information about the gnucash-devel mailing list