Differences between revisions 28 and 29
Revision 28 as of 2009-10-05 05:39:40
Size: 4373
Editor: ?VinceMcIntyre
Comment: Fix arch-specific urls, after correspondence with debbugs maintainer
Revision 29 as of 2009-10-05 06:03:18
Size: 4373
Editor: ?VinceMcIntyre
Comment: make order-by-arch url work
Deletions are marked like this. Additions are marked like this.
Line 12: Line 12:
 * Bugs sorted [[http://bugs.debian.org/cgi-bin/pkgreport.cgi?maint=debian-boot@lists.debian.org;ordering=archfirst|by architecture]].  * Bugs sorted [[http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-boot@lists.debian.org;ordering=archfirst|by architecture]].

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

  • accessibility

  • 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 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 an exhaustive list of tags in regular use. Perhaps we should develop one similar to that used by the KDE team.

Further Processing

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