/[ddp]/manuals/trunk/developers-reference/pkgs.dbk
ViewVC logotype

Diff of /manuals/trunk/developers-reference/pkgs.dbk

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 5222 by lucas, Sat Jun 7 22:36:10 2008 UTC revision 5223 by he, Sun Jun 8 11:20:06 2008 UTC
# Line 662  procedure</ulink>. Line 662  procedure</ulink>.
662  If the bug is real but it's caused by another package, just reassign the bug to  If the bug is real but it's caused by another package, just reassign the bug to
663  the right package.  If you don't know which package it should be reassigned to,  the right package.  If you don't know which package it should be reassigned to,
664  you should ask for help on <link linkend="irc-channels">IRC</link> or  you should ask for help on <link linkend="irc-channels">IRC</link> or
665  on &email-debian-devel;.  Please make sure that the  on &email-debian-devel;.  Please inform the maintainer(s) of the package
666  maintainer(s) of the package the bug is reassigned to know why you reassigned  you reassign the bug to, for example by Cc:ing the message that does the
667  it.  reassign to <email>packagename@packages.debian.org</email> and explaining
668    your reasons in that mail. Please note that a simple reassignment is
669    <emphasis>not</emphasis> e-mailed to the maintainers of the package
670    being reassigned to, so they won't know about it until they look at
671    a bug overview for their packages.
672  </para>  </para>
673  <para>  <para>
674    If the bug affects the operation of your package, please consider
675    cloning the bug and reassigning the clone to the package that really
676    causes the behavior. Otherwise, the bug will not be shown in your
677    package's bug list, possibly causing users to report the same bug over
678    and over again. You should block "your" bug with the reassigned, cloned
679    bug to document the relationship.
680    </para>
681    </listitem>
682    <listitem>
683    <para>
684  Sometimes you also have to adjust the severity of the bug so that it matches  Sometimes you also have to adjust the severity of the bug so that it matches
685  our definition of the severity.  That's because people tend to inflate the  our definition of the severity.  That's because people tend to inflate the
686  severity of bugs to make sure their bugs are fixed quickly.  Some bugs may even  severity of bugs to make sure their bugs are fixed quickly.  Some bugs may even
Legend:
Removed from v.5222  
changed lines
  Added in v.5223
  ViewVC Help
Powered by ViewVC 1.1.5