Differences between revisions 26 and 27
Revision 26 as of 2009-10-03 10:32:01
Size: 3793
Editor: ?VinceMcIntyre
Comment: Point to wiki page. Wording tweaks.
Revision 27 as of 2009-10-03 13:23:23
Size: 4445
Editor: ?VinceMcIntyre
Comment: Add headings. More wording tweaks. Fix serial example, add arch examples.
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
#pragma section-numbers 1
Line 3: Line 4:



~+Bugs in the Installer+~
Line 12: Line 18:
 * How to set usertags is [[http://lists.debian.org/debian-boot/2005/10/msg00229.html|documented in this E-mail]], see also [[bugs.debian.org/usertags| the wiki page]].


~+Tagging Bug Reports+~
Line 15: Line 24:
 * How to set usertags is [[http://lists.debian.org/debian-boot/2005/10/msg00229.html|documented in this E-mail]], see also [[bugs.debian.org/usertags| the wiki page]].
 * Selecting sets of bugs using usertags is not properly documented.
Line 16: Line 27:
Some of the tags we use include: Some of the usertags we have defined include:
Line 23: Line 34:
  * {{{serial}}} : bugs involving serial console installs. [[http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-boot@lists.debian.org;tag=amd64|bts link]]
  * Any Debian architecture for bugs specific to that architecture. (i386, powerpc, etc).
  * {{{serial}}} : bugs involving serial console installs. [[http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-boot@lists.debian.org;tag=serial|bts link]]
  * {{{<arch>}}} : Any Debian architecture for bugs specific to that architecture, e.g. [[http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-boot@lists.debian.org;tag=i386|i386]], [[http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-boot@lists.debian.org;tag=powerpc|powerpc]], etc.
Line 27: Line 38:
The d-i tag should be used only on bugs that are not in packages maintained by debian-boot, but which still affect d-i. (It is not a usertag.) 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 [[http://www.debian.org/Bugs/Developer#tags|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 [[http://pkg-kde.alioth.debian.org/usertags.html|KDE team]].

~+Further Processing+~

Bugs in the Installer

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

  • Bugs in packages maintained by the d-i team, excluding old installation reports and other cruft.

  • Bugs sorted by architecture.

    • Note that bugs may be tagged as applying to more than one architecture, but will only show up once, in the first listed architecture.
  • Here are some links to just display architecture-specific bugs: ?alpha] ?amd64] ?arm] ?hppa] ?i386] ?ia64] ?m68k] ?mips] ?mipsel] ?powerpc] ?s390] ?sparc]

  • Traditional index of bugs.

  • Bugs in other packages in Debian that affect d-i.

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