Differences between revisions 30 and 31
Revision 30 as of 2009-10-05 06:06:27
Size: 4376
Editor: ?VinceMcIntyre
Comment: whitespace change
Revision 31 as of 2009-10-05 06:15:04
Size: 4770
Editor: ?VinceMcIntyre
Comment: explain how to get the full list of usertags. add links for accessibility & usability.
Deletions are marked like this. Additions are marked like this.
Line 33: Line 33:
  * {{{usability}}}
  * {{{accessibility}}}
  * {{{usability}}} : [[http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-boot@lists.debian.org;tag=usability|bts link]]
  * {{{accessibility}}} : [[http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-boot@lists.debian.org;tag=accessibility|bts link]]
Line 38: Line 38:
  * the full list of tags can be found using [[http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-boot@lists.debian.org|this url]]
Line 41: Line 42:
We don't have an exhaustive list of tags in regular use. Perhaps we should develop one similar to that used by the [[http://pkg-kde.alioth.debian.org/usertags.html|KDE team]]. We don't have any more guidance than the list above on which tags to use for what. Perhaps we should develop guidelines similar to that used by the [[http://pkg-kde.alioth.debian.org/usertags.html|KDE team]].

Bugs in the Installer

Some useful views of the DebianInstaller bugs in the bug tracking system:

Tagging Bug Reports

We use usertags to categorise the bugs, with a user of debian-boot@lists.debian.org.

Some of the usertags we have defined include:

  • not-d-i : for bugs that don't actually affect d-i, just some other aspect of a package maintained by debian-boot@lists.debian.org. bts link

  • old-report : for "old" installation reports. bts link

    • FIXME: what criteria are used when applying this?
  • usability : bts link

  • accessibility : bts link

  • serial : bugs involving serial console installs. bts link

  • <arch> : Any Debian architecture for bugs specific to that architecture, e.g. i386, powerpc, etc.

  • debian-edu : bugs affecting only DebianEdu. bts link

  • the full list of tags can be found using this url

The d-i tag should be used only on bugs that are not in packages maintained by the d-i team, but which still affect d-i. (It is a BTS tag not a usertag.)

We don't have any more guidance than the list above on which tags to use for what. Perhaps we should develop guidelines similar to that used by the KDE team.

Further Processing

What to do with the d-i bugs is documented in /BugsPolicy