Re: pseudo-tag management in the bts
On Mon, 15 Sep 2003, Martin Quinson wrote:
> What about a [EASY] tag which we could use to help you isolate the trivial
> bugs? I think about #157437 for example, which is /really/ trivial. (I
> admit, that's the only trivial bug I know for now)
[TRIVIAL]
> And how should I tag the bugs about the performance of the DB? I think about
> #74259, #139838, #160447, #206416, #149760, #179296.
>
> A [PERF] tag could be used to mark the memleaks, also (#47214 even if I
> guess that this leak was solved since it is 3 years old and I seem to
> remember of changes in that area)
Sure, I like that. But note that I have applied 2 performance patchs to dpkg,
the package database and the files database.
For everyone: On an unrelated note, if you find *any* active
bug(open/pending/resolve(but not yet archived)), and it's subject needs to be
tagged, then go ahead.
Reply to: