[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: pseudo-tag management in the bts



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)

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)


Thanks for your time, Mt.

On Sat, Sep 13, 2003 at 11:28:44PM -0500, Adam Heath wrote:
> Tonight, I started doing some major dpkg bug triage.  To faciliate handling
> the large number of bugs, I started retitling lots of them, with the following
> keywords.
> 
> To query these keywords, add '&include=subj:[DOC]', for example.  You can
> specify multiple include(or exclude) options, on the query given to
> pkgreport.cgi.
> 
> The text below will become part of debian/pseudo-tags, which will be installed
> into /usr/share/doc/dpkg.  I'm hoping that if we can follow this procedure, it
> should make working with our bugs much simpler.
> 
> (I haven't retitled all bugs.  The ones I have done were simple to see which
> category they applied to, by reading their existing titles)
> 
> ====
> 
> Below are the list of pseudo-tags we, the Dpkg Team, are using in the
> Debian BTS.  Place as many of the following as apply in the subject(title)
> of your bug report.
> 
> [DOC]                   Documentation bugs, including --help, manpages, and
>                         others
> [ARCH]                  Archtable updates, porting patches
> [INTL]                  Translation updates, or bugs
> [ASSERT]                assert errors
> [UTF-8]                 conversion to utf-8 encoding
> [SEGFAULT]              segfaults
> [CONFFILE]              any issues with conffile handling
> 
> Also, each program that dpkg produces(in any of it's debs) has a
> pseudo-tag for it.
> 
> dpkg.deb:
> [DPKG-SPLIT]
> [DPKG-QUERY]
> [DPKG]
> [DPKG-DEB]
> [MD5SUM]
> [U-A]                   update-alternatives
> [INSTALL-INFO]
> [DPKG-DIVERT]
> [DPKG-STATOVERRIDE]
> [CLEANUP-INFO]
> [S-S-D]                 start-stop-daemon
> 
> dpkg-dev.deb:
> [DPKG-NAME]
> [DPKG-SOURCE]
> [DPKG-GENCHANGES]
> [DPKG-GENCONTROL]
> [DPKG-SHLIBDEPS]
> [DPKG-BUILDPACKAGE]
> [DPKG-DISTADDFILE]
> [822-DATE]
> [DPKG-SCANPACKAGES]
> [DPKG-SCANSOURCES]
> [DPKG-ARCHITECTURE]
> [DPKG-PARSECHANGELOG]
> [DPKG-CHECKBUILDDEPS]
> 
> dselect.deb:
> [DSELECT]
> 
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-dpkg-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> 
> 

-- 
If the automobile had followed the same development cycle as the computer, a
Rolls-Royce today would cost $100, get a million miles to the gallon, and
explode once every few weeks, killing everyone inside.



Reply to: