| 160 |
Generally you should deal with bug reports on your packages as described in |
Generally you should deal with bug reports on your packages as described in |
| 161 |
<xref linkend="bug-handling"/> . However, there's a special category of bugs |
<xref linkend="bug-handling"/> . However, there's a special category of bugs |
| 162 |
that you need to take care of — the so-called release-critical bugs (RC |
that you need to take care of — the so-called release-critical bugs (RC |
| 163 |
bugs). All bug reports that have severity <emphasis>critical</emphasis>, |
bugs). All bug reports that have severity <literal>critical</literal>, |
| 164 |
<emphasis>grave</emphasis> or <emphasis>serious</emphasis> are considered to |
<literal>grave</literal> or <literal>serious</literal> are considered to |
| 165 |
have an impact on whether the package can be released in the next stable |
have an impact on whether the package can be released in the next stable |
| 166 |
release of Debian. These bugs can delay the Debian release and/or can justify |
release of Debian. These bugs can delay the Debian release and/or can justify |
| 167 |
the removal of a package at freeze time. That's why these bugs need to be |
the removal of a package at freeze time. That's why these bugs need to be |
Parent Directory
| 
Revision Log
| 
Patch