forked from gelosie/jdic
-
Notifications
You must be signed in to change notification settings - Fork 0
/
reportbug.html
executable file
·352 lines (201 loc) · 10.2 KB
/
reportbug.html
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
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=windows-1252">
<TITLE>Reporting Bugs</TITLE>
<META NAME="GENERATOR" CONTENT="StarOffice 7 (Win32)">
<META NAME="CREATED" CONTENT="20031215;391548">
<META NAME="CHANGEDBY" CONTENT="Roger Brinkley">
<META NAME="CHANGED" CONTENT="20040528;16252144">
<STYLE>
<!--
H1 { margin-left: 0.25in; margin-right: 0.25in; color: #000000 }
P { margin-left: 0.25in; margin-right: 0.25in; color: #000000 }
-->
</STYLE>
</HEAD>
<BODY LANG="en-US" TEXT="#000000" BGCOLOR="#ffffff" DIR="LTR">
<!-- etracker PARAMETER 2.0.1 -->
<script type="text/javascript">
var et_easy = 0;
var et_ssl = 1;
var et_pagename = "Reporting%20Bugs";
var et_areas = "";
var et_ilevel = 0;
</script>
<!-- etracker PARAMETER END -->
<!-- etracker CODE 2.0.6 -->
<script type="text/javascript">
var et_server="https://www.etracker.de";
var et_sslserver="https://www.etracker.de";
var et_referer=et_server+"/soverview.php?c=1&et=";
var et_sw,et_sc="na";var et_pl,tmp,cex="";if(navigator.appName==
'Netscape'||navigator.appName=='Opera'){for(i=0;i<navigator.plugins.length;++i)
et_pl+=navigator.plugins[i].name+';';et_pl=escape(et_pl);}function et_pQ(param)
{var ll,fl;var qS,pV,rS;qS=document.location.search;pV="";if(qS.length>1){qS=qS.
substr(1);fl=qS.indexOf(param);if(fl!=-1){fl+=param.length+1;ll=qS.indexOf('&',
fl);if(ll==-1) ll=qS.length;pV=qS.substring(fl,ll);rS=new RegExp(" ","g");pV=
pV.replace(rS,"+");f1=pV.indexOf('=',0);pV=pV.substring(f1+1);}} return pV;}
function et_eC(param){var et_a='',et_t='',et_p='';var et_ref=escape(document.
referrer);if(typeof(top.document)=="object")et_ref=escape(top.document.referrer);
if(et_ref!="")et_ref="&ref="+et_ref;et_sw="&swidth="+et_sw;et_sc=
"&scolor="+et_sc;if(et_easy)et_easy="&et_easy=1";else et_easy="";if(
et_pl!="")et_pl="&p="+et_pl;if(et_areas!="")et_a="&et_areas="+
escape(et_areas);if(typeof(et_target)=="undefined"||typeof(et_target)==
"unknown"){et_target="";et_tval="0";et_tonr="0";et_tsale=0;}if(typeof(
et_lpage)=="undefined"||typeof(et_lpage)=="unknown")et_lpage="";else
et_lpage="&et_lpage="+et_lpage;if(typeof(et_trig)=="undefined"||typeof(
et_trig)=="unknown")et_trig="";if(et_trig!="")cex="&et_trig="+
et_trig;if((tc=et_pQ("et_cid"))&&(tl=et_pQ("et_lid")))cex=cex+"&et_cid="+
tc+"&et_lid="+tl;if(tmp=et_pQ("et_target")||et_target!=""){tv=et_pQ
("et_tval");to=et_pQ("et_tonr");ts=et_pQ("et_tsale");et_t="&et_target="+
escape(tmp.length?tmp:et_target)+","+(tv?tv:et_tval)+","+(to?to:et_tonr)+
","+(ts?ts:et_tsale);}if(et_pagename!="")et_p="&et_pagename="+escape(
et_pagename);tc=new Date();document.write("<a target='_blank' href='"+et_referer+
param+"'><img border='0' alt='' src='"+(et_ssl==1?et_sslserver:et_server)+
"/cnt.php?java=y&tc="+tc.getTime()+"&et="+param+"&et_ilevel="+
et_ilevel+et_easy+et_p+et_a+cex+et_t+et_lpage+et_sw+et_sc+et_ref+et_pl+"'/>"+
"<\/a>");}</script><script type="text/javascript1.2">et_sw=screen.width;et_sc=
navigator.appName!='Netscape'?screen.colorDepth:screen.pixelDepth;</script>
<script type="text/javascript">et_eC('ir339g');</script>
<!-- etracker CODE NOSCRIPT -->
<noscript>
<a target="_blank" href="https://www.etracker.de/soverview.php?c=1&et=ir339g">
<img border="0" alt="" src="https://www.etracker.de/cnt.php?et=ir339g&java=n&
et_easy=0&et_pagename=Reporting%20Bugs&et_areas=&et_ilevel=&
et_target=&et_lpage=&et_trig="/></a>
</noscript>
<!-- etracker CODE END -->
<H1>How to Write a Good Bug Report?
</H1>
<P>To increase the chances that the bug you're reporting will be
addressed in a timely manner, you should adhere to the following
guidelines:
</P>
<OL>
<LI><P>When you encounter a behavior which might potentially be a
bug, try to collect as much relevant data as possible (e.g. take a
screenshot in case of a UI problem, generate a thread-dump in case
of a deadlock or serious performance degradation, create copies of
relevant files, etc.) and try to recall and note the actions you
performed right before the problem occurred.</P>
<LI><P>Try to restore the original state (if possible) and reproduce
the incorrect behavior using the steps you noted. This should help
you to determine whether the problem is reproducible and persistent
or just intermittent. This is not to say intermittent problems
shouldn't be reported, but it's always worth pointing it out in the
bug report to make the evaluators aware of this fact.</P>
<LI><P>There is a chance that someone already reported the bug
you've just encountered. Therefore, it's a good idea to search the
bug database first. Go to the the JDIC Issue Tracking page, fill-in
the query parameters that seem relevant to your case, submit the
form, and go through the returned list of issues to see if any of
them match your problem. Typically, you'll want to search for issues
of type <I>DEFECT</I>, in an open state (<I>NEW</I>, <I>STARTED</I>,
<I>REOPENED</I>) with a specific string in the <B>Summary</B> and/or
<B>Description</B> fields. If the bug already exists in the database
and you still think you have some useful info to share, it is highly
recommended to add this info to the existing issue instead of filing
a new one.</P>
<LI><P>If you assume the bug hasn't been reported yet, it's time to
enter a new bug. (Note: to be able to do so and to be able to
add/update information in the issue database, you need to have a
netbeans.org account and be logged in. If you don't have an account
yet, you'll have to <A HREF="https://www.dev.java.net/servlets/Join">register</A>
and then become a member of the JDIC project.).</P>
<UL>
<LI><P>The first thing you need to do is to select the <B>Component</B>
to file the bug against.
</P>
<LI><P>After selecting the component, you'll be prompted to fill in
the following fields:</P>
<UL>
<LI><P><B>Version</B> - choose the version of the component in
which you encountered the problem. In case of a problem found in a
development build, select the next release version number, or
<I>current</I>.</P>
<LI><P><B>Subcomponent</B> - select the subcomponent of a given
component. If you're not sure, just select <I>code</I>.</P>
<LI><P><B>Platform</B> - select the platform you were using when
the problem occured. If you were able to reproduce it on multiple
platforms, or are positively sure the behavior is platform
independent, use <I>All</I>.</P>
<LI><P><B>OS</B> - similar to the <B>Platform.</B></P>
<LI><P><B>Priority</B> - use this field to indicate the urgency
and severity of the issue. Refer to <A HREF="bug_priority_guidelines.html">Bug
Priority Guidelines</A> for instructions how to set the priority
level appropriately. If you're still in doubt, it's better to
stick with the default P3 value.</P>
<LI><P><B>Issue Type</B> - select the type of issue you're
reporting. In most cases, you'll probably want to use <I>DEFECT</I>
(when reporting a bug) or <I>ENHANCEMENT</I> (when requesting an
enhancement or feature).</P>
<LI><P><B>Assigned To</B> - unless you're absolutely sure who this
issue should be assigned to, leave this field blank. The bug will
be automatically assigned to the component (subcomponent) owner.</P>
<LI><P><B>Cc</B> - enter an optional comma-separated list of email
aliases you want to be notified about this issue and any
subsequent changes to its status. You as the reporter will be
notified automatically, so there's no need to add yourself. The
aliases must refer to valid netbeans.org accounts (e.g.
<I>[email protected]</I>). Arbitrary email addresses are not
accepted by the system.</P>
<LI><P><B>URL</B> - if there is a URL relevant to this issue, you
can type it here. In most cases, this field will be blank.</P>
<LI><P STYLE="margin-bottom: 0in"><B>Summary</B> - a brief (one
sentence) description of the issue. You should try to make it as
specific as possible while keeping it short (70 characters at the
most).
</P>
<LI><P><B>Description</B> - a detailed description of the problem.
The description should include the following information:</P>
<UL>
<LI><P STYLE="margin-bottom: 0in">the build number
</P>
<LI><P STYLE="margin-bottom: 0in">JDK version
</P>
<LI><P STYLE="margin-bottom: 0in">observed behavior
</P>
<LI><P STYLE="margin-bottom: 0in">expected behavior
</P>
<LI><P STYLE="margin-bottom: 0in">exact steps to reproduce the
problem
</P>
<LI><P>any other information potentially related to the issue
</P>
</UL>
<P>Please note that you should not paste larger chunks of text
(e.g. complete exception logs and thread dumps, source files, test
data, etc.) into the Description field. You should always provide
those files in the form of attachments (see below). There is one
exception to this rule: although including complete exception logs
in Description is not recommended, it is a good idea to copy the
relevant part of the stack trace (usually 4-6 top lines to the
field to allow for easy searching.</P>
</UL>
<LI><P>After completing the form, push the <B>Commit</B> button to
send it to the database. As a confirmation you will see a number
uniquely identifying the issue you've just filed.</P>
<LI><P>If you have some additional files relevant to the issue,
click on the <B>Add Attachment</B> link in the page you get after
the previous step. You'll be asked to provide the following info:</P>
<UL>
<LI><P STYLE="margin-bottom: 0in">the location of file to be
sumbitted on your local machine
</P>
<LI><P STYLE="margin-bottom: 0in">a one-line description of the
attachment
</P>
<LI><P>the type of file being attached (plain text, diff, HTML,
GIF, JPEG, PNG, binary)
</P>
</UL>
<P>Push the <B>Submit</B> button to attach the file to the issue
report.</P>
</UL>
<LI><P>Should you have any questions or comments regarding the issue
handling process, please contact the JDIC <A HREF="mailto:[email protected]">issues</A>
mailing list..</P>
</OL>
</BODY>
</HTML>