home *** CD-ROM | disk | FTP | other *** search
/ Mac Easy 2010 May / Mac Life Ubuntu.iso / casper / filesystem.squashfs / usr / share / gimp / 2.0 / help / en / apbs03.html < prev    next >
Encoding:
Extensible Markup Language  |  2008-05-03  |  11.8 KB  |  278 lines
  1. <?xml version="1.0" encoding="UTF-8" standalone="no"?>
  2. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
  3. <html xmlns="http://www.w3.org/1999/xhtml">
  4.   <head>
  5.     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
  6.     <title>3.¬† What Happens to a Bug Report after you Submit it</title>
  7.     <link rel="stylesheet" href="gimp-help-plain.css" type="text/css" />
  8.     <link rel="stylesheet" href="gimp-help-screen.css" type="text/css" />
  9.     <link rel="stylesheet" href="gimp-help-custom.css" type="text/css" />
  10.     <link rel="alternate stylesheet" href="gimp22.css" type="text/css" title="gimp22" />
  11.     <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" />
  12.     <link rel="start" href="index.html" title="GNU Image Manipulation Program" />
  13.     <link rel="up" href="gimp-introduction-bugs.html" title="Appendix¬†B.¬† Reporting Bugs and Requesting Enhancements" />
  14.     <link rel="prev" href="apbs02.html" title="2.¬† Reporting the Bug" />
  15.     <link rel="next" href="legal.html" title="Appendix¬†C.¬† GNU Free Documentation License" />
  16.   </head>
  17.   <body>
  18.     <div class="navheader">
  19.       <table width="100%" summary="Navigation header">
  20.         <tr>
  21.           <th colspan="3" align="center">3.¬†
  22.       <span lang="en" xml:lang="en">
  23.         What Happens to a Bug Report after you Submit it
  24.       </span>
  25.     </th>
  26.         </tr>
  27.         <tr>
  28.           <td width="20%" align="left"><a accesskey="p" href="apbs02.html"><img src="../images/prev.png" alt="Prev" /></a>¬†</td>
  29.           <th width="60%" align="center">Appendix¬†B.¬†
  30.     <span lang="en" xml:lang="en">Reporting Bugs and Requesting Enhancements</span>
  31.   </th>
  32.           <td width="20%" align="right">¬†<a accesskey="n" href="legal.html"><img src="../images/next.png" alt="Next" /></a></td>
  33.         </tr>
  34.       </table>
  35.       <hr />
  36.     </div>
  37.     <div class="sect1" lang="en" xml:lang="en">
  38.       <div class="titlepage">
  39.         <div>
  40.           <div>
  41.             <h2 class="title" style="clear: both"><a id="id2807319"></a>3.¬†
  42.       <span lang="en" xml:lang="en">
  43.         What Happens to a Bug Report after you Submit it
  44.       </span>
  45.     </h2>
  46.           </div>
  47.         </div>
  48.       </div>
  49.       <p>
  50.       At any time after it is submitted, a bug report has a
  51.       ‚Äú<span class="quote">Status</span>‚Äù
  52.       that describes how it is currently being handled.  Here are the
  53.       possible values of <span class="emphasis"><em>Status</em></span> and what they mean:
  54.     </p>
  55.       <div class="variablelist">
  56.         <dl>
  57.           <dt>
  58.             <span class="term">Unconfirmed</span>
  59.           </dt>
  60.           <dd>
  61.             <p>
  62.             This is the initial status of a bug report, from the time it is
  63.             submitted until one of the maintainers reads it and decides
  64.             whether it is really a valid bug report. Sometimes the maintainers
  65.             aren't sure, and in the meantime leave the status as
  66.             ‚Äú<span class="quote">Unconfirmed</span>‚Äù. In the worst cases, a bug report can
  67.             stay
  68.             unconfirmed for a year or longer, but this is considered a bad
  69.             thing and does not happen very often.
  70.           </p>
  71.           </dd>
  72.           <dt>
  73.             <span class="term">New</span>
  74.           </dt>
  75.           <dd>
  76.             <p>
  77.             This means that the bug report has been read by one of the
  78.             maintainers, and is considered, for the moment at least, to be
  79.             valid. It does not necessarily mean that anything is going to be
  80.             done about it immediately: some bug reports, especially
  81.             enhancement requests, may be perfectly valid and still go for a
  82.             long time before anybody is able to deal with them. Many bugs, on
  83.             the other hand, are fixed within hours of being reported.
  84.           </p>
  85.           </dd>
  86.           <dt>
  87.             <span class="term">Assigned</span>
  88.           </dt>
  89.           <dd>
  90.             <p>
  91.             This means that a specific person has agreed to work on the bug.
  92.             It does not, this world being the kind of world that it is, mean
  93.             that that person will actually <span class="emphasis"><em>do</em></span>
  94.             anything in particular, so for practical purposes this status
  95.             means nearly the same thing as ‚Äú<span class="quote">New</span>‚Äù.
  96.           </p>
  97.           </dd>
  98.           <dt>
  99.             <span class="term">Reopened</span>
  100.           </dt>
  101.           <dd>
  102.             <p>
  103.             This means that the bug report was at some point considered by the
  104.             maintainers to be resolved (i.e., finished), but new information
  105.             came in that caused them to change their minds: most likely, a
  106.             change that was intended to fix the problem did not completely
  107.             work.
  108.           </p>
  109.           </dd>
  110.           <dt>
  111.             <span class="term">Needinfo</span>
  112.           </dt>
  113.           <dd>
  114.             <p>
  115.             This is a status you should pay particular attention to. It means
  116.             that you did not supply enough information in your bug report to
  117.             enable anything to be done about it. In most cases, no further
  118.             action will be taken on the bug report until you supply additional
  119.             information (by adding a comment). If too much time goes by
  120.             without any input from you, the bug report will eventually be
  121.             resolved as ‚Äú<span class="quote">Incomplete</span>‚Äù.
  122.           </p>
  123.           </dd>
  124.           <dt>
  125.             <span class="term">Resolved</span>
  126.           </dt>
  127.           <dd>
  128.             <p>
  129.             This means that the maintainers believe that they have finished
  130.             dealing with the bug report. If you disagree, you can re-open it,
  131.             but since you cannot force anybody to work on a bug against their
  132.             will, you should have a good reason for doing so. Bugs can be
  133.             resolved in a variety of ways. Here are the possible values of
  134.             <span class="emphasis"><em>Resolution</em></span> and what they mean:
  135.           </p>
  136.             <div class="variablelist">
  137.               <dl>
  138.                 <dt>
  139.                   <span class="term">Fixed</span>
  140.                 </dt>
  141.                 <dd>
  142.                   <p>
  143.                   The bug report is considered valid, and
  144.                   <acronym class="acronym">GIMP</acronym> has been
  145.                   changed in a way that is considered to fix it.
  146.                 </p>
  147.                 </dd>
  148.                 <dt>
  149.                   <span class="term">Wontfix</span>
  150.                 </dt>
  151.                 <dd>
  152.                   <p>
  153.                   The maintainers agree that the bug report is valid, but it
  154.                   would take so much effort to fix, in relation to its
  155.                   importance, that it is not worth the trouble.
  156.                 </p>
  157.                 </dd>
  158.                 <dt>
  159.                   <span class="term">Duplicate</span>
  160.                 </dt>
  161.                 <dd>
  162.                   <p>
  163.                   This means that the same bug has already been reported by
  164.                   somebody else. If you see this resolution, you will also see
  165.                   a pointer to the earlier bug report, which will often give
  166.                   you a lot of useful information.
  167.                 </p>
  168.                 </dd>
  169.                 <dt>
  170.                   <span class="term">Notabug</span>
  171.                 </dt>
  172.                 <dd>
  173.                   <p>
  174.                   This means that the behavior described in the bug
  175.                   report is intentional. It may seem like a bug to you
  176.                   (and there may be many people who agree with you), but
  177.                   the program is working the way it was intended to
  178.                   work,  and the developers don't want to change it.
  179.                 </p>
  180.                 </dd>
  181.                 <dt>
  182.                   <span class="term">NotGnome</span>
  183.                 </dt>
  184.                 <dd>
  185.                   <p>
  186.                   The bug report is valid, but it can't be addressed by
  187.                   changing <acronym class="acronym">GIMP</acronym>. Problems in operating
  188.                   systems, window managers, or libraries that
  189.                   <acronym class="acronym">GIMP</acronym> depends on will often be
  190.                   given this resolution. Sometimes the next appropriate step
  191.                   is to file a bug report for the software that is really at
  192.                   fault.
  193.                 </p>
  194.                 </dd>
  195.                 <dt>
  196.                   <span class="term">Incomplete</span>
  197.                 </dt>
  198.                 <dd>
  199.                   <p>
  200.                   The bug report did not contain enough information for
  201.                   anything to be done about it, and the reporter did not
  202.                   respond to requests for more information. Usually a bug
  203.                   report will be open for at least a month or two before it is
  204.                   resolved in this way.
  205.                 </p>
  206.                 </dd>
  207.                 <dt>
  208.                   <span class="term">Invalid</span>
  209.                 </dt>
  210.                 <dd>
  211.                   <p>
  212.                   Something is wrong with the form of the bug report: most
  213.                   commonly, the reporter has accidentally submitted the same
  214.                   bug report multiple times. (This can easily happen by
  215.                   mistake with some web browsers.) Bug reports that
  216.                   incorrectly describe how the program behaves may also be
  217.                   resolved as Invalid.
  218.                 </p>
  219.                 </dd>
  220.               </dl>
  221.             </div>
  222.             <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
  223.               <table border="0" summary="Note">
  224.                 <tr>
  225.                   <td rowspan="2" align="center" valign="top" width="25">
  226.                     <img alt="[Note]" src="../images/note.png" />
  227.                   </td>
  228.                   <th align="left">Note</th>
  229.                 </tr>
  230.                 <tr>
  231.                   <td align="left" valign="top">
  232.                     <p>
  233.               If you disagree with the resolution of a bug report, you are
  234.               always free to add your comments to it. Any comment added to any
  235.               bug report, resolved or not, causes email to be sent to the
  236.               <acronym class="acronym">GIMP</acronym>
  237.               Bugzilla mailing list, so it will at least be seen by the
  238.               maintainers. This does not, of course, mean that they will
  239.               necessarily respond to it.
  240.             </p>
  241.                   </td>
  242.                 </tr>
  243.               </table>
  244.             </div>
  245.           </dd>
  246.         </dl>
  247.       </div>
  248.     </div>
  249.     <div class="navfooter">
  250.       <hr />
  251.       <table width="100%" summary="Navigation footer">
  252.         <tr>
  253.           <td width="40%" align="left"><a accesskey="p" href="apbs02.html"><img src="../images/prev.png" alt="Prev" /></a>¬†</td>
  254.           <td width="20%" align="center">
  255.             <a accesskey="u" href="gimp-introduction-bugs.html">
  256.               <img src="../images/up.png" alt="Up" />
  257.             </a>
  258.           </td>
  259.           <td width="40%" align="right">¬†<a accesskey="n" href="legal.html"><img src="../images/next.png" alt="Next" /></a></td>
  260.         </tr>
  261.         <tr>
  262.           <td width="40%" align="left" valign="top"><a accesskey="p" href="apbs02.html">2.¬†
  263.       <span lang="en" xml:lang="en">Reporting the Bug</span>
  264.     </a>¬†</td>
  265.           <td width="20%" align="center">
  266.             <a accesskey="h" href="index.html">
  267.               <img src="../images/home.png" alt="Home" />
  268.             </a>
  269.           </td>
  270.           <td width="40%" align="right" valign="top">¬†<a accesskey="n" href="legal.html">Appendix¬†C.¬†
  271.     <span lang="en" xml:lang="en">GNU Free Documentation License</span>
  272.   </a></td>
  273.         </tr>
  274.       </table>
  275.     </div>
  276.   </body>
  277. </html>
  278.