Differences between revisions 34 and 35
Revision 34 as of 2018-10-17 20:32:16
Size: 5417
Comment:
Revision 35 as of 2018-10-17 20:34:50
Size: 5516
Comment:
Deletions are marked like this. Additions are marked like this.
Line 22: Line 22:
[[http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-boot@lists.debian.org;tag=s390|s390]]

Bugs in the Installer

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

armhf arm64 hppa i386 ia64 m68k mips mipsel mips64el powerpc ppc64el s390 s390x sparc

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 or via UDD

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