.gitignore | 2 + howtos/triage-bugs.mdwn | 85 ++++++++++++++++++++++++++++++++++++++++++++++++ index.mdwn | 1 3 files changed, 88 insertions(+)
New commits: commit 6d9bde40c5dfe71e841f9dfb2a47f14e3e244def Author: Cyril Brulebois <k...@debian.org> Date: Sun Jan 16 04:19:00 2011 +0100 index: Link to triage-bugs. diff --git a/index.mdwn b/index.mdwn index 602d3ff..61496b9 100644 --- a/index.mdwn +++ b/index.mdwn @@ -3,6 +3,7 @@ ## Howtos * [How to report bugs](howtos/report-bugs.html) + * [How to triage bugs](howtos/triage-bugs.html) * [How to use GDB](howtos/use-gdb.html) * [How to configure outputs](howtos/use-xrandr.html) commit 2d27e73ab5b6ebb47aeacf514dc3332d6663ad3f Author: Cyril Brulebois <k...@debian.org> Date: Sun Jan 16 04:17:54 2011 +0100 triage-bugs: Add ideas about categories. diff --git a/howtos/triage-bugs.mdwn b/howtos/triage-bugs.mdwn index f3b0ab6..116cad6 100644 --- a/howtos/triage-bugs.mdwn +++ b/howtos/triage-bugs.mdwn @@ -39,3 +39,47 @@ Let’s give some examples: Here’s an example of URL, for the last tag: <http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-x@lists.debian.org&tag=squeeze-candidate> +— by the way one should keep an eye on the list of found/fixed +versions since those bugs are likely marked as resolved (in `unstable` +or `experimental`), but might still affect a stable release. Maybe we +just need to have both `squeeze-candidate` and `squeeze-accepted`, and +swap usertags when the stable upload happens. + + +## Categories + +The BTS has yet another feature which can help, categories. That’s +based on usertags as well, but one has to use the package address +(`$pack...@packages.debian.org`), so that’s package-specific rather +than team-specific. + +Categories are +[documented on the wiki](http://wiki.debian.org/bugs.debian.org/usertags), +and they would probably be welcome in the `intel` and `ati` cases +above, as well as in the “multiple tools in a single bundle” +cases.. An example of what we could achieve is the +[devscripts bug page](http://bugs.debian.org/devscripts) (it takes +some time to load, plenty of bugs). + +Needed steps for that to happen: + + * create usercategories. + * move usertags from `debian-x@lists.debian.org` to + `$pack...@packages.debian.org`, probably using the `bts select` + command to get the list over which to iterate: + * profit! + +To move the usertags, something like that should do the job: + + # Adding usertags: + user $packa...@packages.debian.org + usertag X xset + usertag Y xrandr + user $packa...@packages.debian.org + usertag Z i810 + + # Removing tags which are no longer needed: + user debian-x@lists.debian.org + usertag X - xset + usertag Y - xrandr + usertag Z - i810 commit b2d02575579b921452726e22f8d0124736e3a703 Author: Cyril Brulebois <k...@debian.org> Date: Sun Jan 16 04:17:36 2011 +0100 triage-bugs: Cosmetics. diff --git a/howtos/triage-bugs.mdwn b/howtos/triage-bugs.mdwn index a226a07..f3b0ab6 100644 --- a/howtos/triage-bugs.mdwn +++ b/howtos/triage-bugs.mdwn @@ -4,11 +4,16 @@ It’d be nice to get all upstream bugs tagged as such (`upstream` tag), forwarded upstream (<http://bugs.freedesktop.org/> for most packages), -and marked as such -(`forwarded X https://bugs.freedesktop.org/show_bug.cgi?id=Y`). +and marked as such. -Then `bts-link` comes into play and help us tracking upstream status, -which is pretty nice to have. +A mail to `cont...@bugs.debian.org` would look like: + + tag X upstream + forwarded X https://bugs.freedesktop.org/show_bug.cgi?id=Y + thanks + +Then [`bts-link`](http://bts-link.alioth.debian.org/) comes into play +and help us tracking upstream status, which is pretty nice to have. ## Usertags commit 613163f6b97d1b2822515a37fdc4f0408e44fb60 Author: Cyril Brulebois <k...@debian.org> Date: Sun Jan 16 03:48:35 2011 +0100 Ignore generated html and pdf files. diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..23f832b --- /dev/null +++ b/.gitignore @@ -0,0 +1,2 @@ +*.html +*.pdf commit 700dfdef3d2a83e09f1c5b11ba5012ec0bd338e1 Author: Cyril Brulebois <k...@debian.org> Date: Sun Jan 16 03:47:44 2011 +0100 Start a doc about bug triaging. diff --git a/howtos/triage-bugs.mdwn b/howtos/triage-bugs.mdwn new file mode 100644 index 0000000..a226a07 --- /dev/null +++ b/howtos/triage-bugs.mdwn @@ -0,0 +1,36 @@ +# How to triage bugs + +## Packaging bugs or upstream bugs? + +It’d be nice to get all upstream bugs tagged as such (`upstream` tag), +forwarded upstream (<http://bugs.freedesktop.org/> for most packages), +and marked as such +(`forwarded X https://bugs.freedesktop.org/show_bug.cgi?id=Y`). + +Then `bts-link` comes into play and help us tracking upstream status, +which is pretty nice to have. + + +## Usertags + +Another feature of the BTS is usertagging. That lets people keep track +of additional tags, “attached” to a given mail address. For XSF, +that’s `debian-x@lists.debian.org`. + +The list of all usertagged bugs can be seen on: +<http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-x@lists.debian.org>; +the list of all used usertags is at the bottom, in the form. + +Let’s give some examples: + + * `i810`, `i915`: helps triaging `-video-intel` bugs depending on the + chipset. + * `r200`, `r300`: ditto for `-video-ati`. + * `xset`, `xrandr`: helps triaging `x11-xserver-utils` bugs depending + on the affected tool (like other `x11-*` packages, that’s a bundle + of teeny tiny apps). + * `squeeze-candidate`: helps keeping a list of bugs we’d like to get + fixed in a point release (through a stable update). + +Here’s an example of URL, for the last tag: +<http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-x@lists.debian.org&tag=squeeze-candidate> -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1pej9b-0000kh...@alioth.debian.org