2,569
edits
Changes
Jump to navigation
Jump to search
mLine 3:
Line 3: − + − − General Instructions for using the bug Tracker are here [http://www.bugzilla.org/docs/tip/html/using.html Using Bugzilla] + Line 22:
Line 21: − + + Line 45:
Line 45: − + Line 51:
Line 51: − + Line 78:
Line 78: − − At the appropriate stage change the Status to 'Resolved - Fixed' or 'Resolved - Verified' − − Note. We don't expect you to change Bugzilla resolutions and flags if you are all doubtful about doing that, but everyone has to start somewhere so have a go. Line 93:
Line 89: − + Line 183:
Line 179: − + + + + Line 195:
Line 194: − − If you can help do these steps, the developers could concentrate on fixing the bugs. − The list above is maybe 90% of the time of most bugs. Help pitch in and do the first 90% of the work.
no edit summary
You don't have to be a programmer to help or use the bug tracker.
You don't have to be a programmer to help or use the bug tracker.
Bugs also include fixing things and making suggestions on documentation, translations and the SME Server web sites.
Bugs also include fixing and making suggestions on documentation, translations and the SME Server web sites.
General Instructions for using the bug Tracker are here http://www.bugzilla.org/docs/tip/html/using.html
===Searching for bugs===
===Searching for bugs===
typically you may restrict Product to use '7.x/Future/Documentation' <br />
typically you may restrict Product to use '7.x/Future/Documentation' <br />
and enter a search term into either 'Summary' or 'A Comment'
and enter a search term into either 'Summary' or 'A Comment' <br />
In Comment, toggle between 'contains the string' 'contains all the words' ' contains any of the words' etc.
eg. Status = CLOSED, Resolution = WONTFIX, Summary = yum <br />
eg. Status = CLOSED, Resolution = WONTFIX, Summary = yum <br />
===Reporting Bugs===
===Reporting Bugs===
Please help us to make our software as reliable as possible. Your role in that is to report possible bugs only via the bug tracker, and to encourage others to do the same. Thanks.
Please help us to make our software as reliable as possible. Your role in that is to report possible bugs only via the bug tracker, and to encourage others to do the same.
Everyone reporting bugs needs to read:
Everyone reporting bugs needs to read:
Also see [http://www.bugzilla.org/docs/tip/html/bugreports.html#fillingbugs Reporting a New Bug]
Also see [http://www.bugzilla.org/docs/tip/html/bugreports.html#fillingbugs Reporting a New Bug]
If you have searched the Manual and Bug Tracker and not found an answer or someone else's report that matches yours, you should register on the Bug Tracker and enter a new bug. The debugging process of any issue requires active participation on the part of the reporter, providing further information and clarification of the problem.
If you have searched the wiki, forum and Bug Tracker and not found an answer or someone else's report that matches yours, you should register on the Bug Tracker and enter a new bug. The debugging process of any issue requires active participation on the part of the reporter, providing further information and clarification of the problem.
To enter a bug choose a category, component, fill in the details of the bug, and commit.
To enter a bug choose a category, component, fill in the details of the bug, and commit.
* then change the Status to 'Resolved - Fixed'.
* then change the Status to 'Resolved - Fixed'.
* let someone else verify, or verify someone else's work
* let someone else verify, or verify someone else's work
===Bug Status===
===Bug Status===
[http://www.bugzilla.org/docs/tip/html/lifecycle.html Lifecycle of a Bug]
[http://www.bugzilla.org/docs/tip/html/lifecycle.html Lifecycle of a Bug]
Resolution status:
Resolution status:
* NEW
* NEW
Once bugs are confirmed, '''by anyone''' see note above, change status to new,
Once bugs are confirmed, '''by anyone''' see note above, change the status to new,
----
----
===Bug Triage===
===Bug Triage===
Reread http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
If you can help do these steps, the developers can concentrate on fixing the bugs. <br >
The steps in this list is maybe 90% of the time of most bugs.
Reread [http://www.chiark.greenend.org.uk/~sgtatham/bugs.html How to report bugs effectively]
Now look at the bug reports in Bugzilla with your developer hat on.
Now look at the bug reports in Bugzilla with your developer hat on.
* Add a note about a workaround/fix if one is obvious to you
* Add a note about a workaround/fix if one is obvious to you
* That fix may not be the one we adopt, but it often helps if you tell us what you did to fix it
* That fix may not be the one we adopt, but it often helps if you tell us what you did to fix it