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