[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[wtp-dev] What has been fixed reports and bug repoting conventions
|
We have started automatically generating a what is fixed report with
each build. This report uses your CVS comments and uses bugzilla to
cross-check and retrive bug attributes to generate a report.
http://download.eclipse.org/webtools/committers/drops/I-I200601291054-200601291054/whatisfixed/buglog.html
The lists are quite accurate but can miss some bugs due the following
reasons.
1) To make the list bug must be targeted (1.0 M1.01.1 for 101, or 1.0
M1.01, 1.5 M4, 1.5 M5, 1.5 M6 for 1.5 stream)
2) Its status must be resolved/fixed (currently we relaxed this criteria
to include all bugs targeted and has an associated CVS activity)
3) You must add a comment to your CVS commit with the bug number [#bug
no]. Not following convention can also lead to incorrect results. Some
examples are provided. We can try to be bit relaxed with our parsing,
but the best solution is to follow convention :-)
[bugzilla down]
[nobug]:[some comment that has nothing to do with a bug in square brackets]
[Bug 112334]
[NO BUG]
[nobug]
[112333 ] (space)
[ 112333 ] (space)
[112333-123456, 123456] (multiple with seperators)
[112213 no bracket
121244 no bracket
--
Naci Dai,
eteration a.s.
Inonu cad. Sumer sok. Zitas D1-15
Kozyatagi, Istanbul 34742
+90 (533) 580 2393 (cell)
+90 (216) 361 5434 (phone)
+90 (216) 361 2034 (fax)
http://www.eteration.com/
mailto:nacidai@xxxxxxx
mailto:naci@xxxxxxxxxxxxx
