2,569
edits
Changes
Jump to navigation
Jump to search
Line 4:
Line 4: − − [http://www.bugzilla.org/docs/tip/html/using.html General Instructions] − for using the bug Tracker Line 71:
Line 68: − + − + +
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 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.
===Bug Categories===
===Bug Categories===
[http://www.chiark.greenend.org.uk/~sgtatham/bugs.html How to report bugs effectively]
[http://www.chiark.greenend.org.uk/~sgtatham/bugs.html How to report bugs effectively]
Also see [http://www.bugzilla.org/docs/tip/html/bugreports.html#fillingbugs Reporting a New Bug] and
Also see [http://www.bugzilla.org/docs/tip/html/using.html General Instructions] ,
[http://bugs.contribs.org/page.cgi?id=bug-writing.html Bug Writing]
[http://www.bugzilla.org/docs/tip/html/bugreports.html#fillingbugs Reporting a New Bug]
and [http://bugs.contribs.org/page.cgi?id=bug-writing.html Bug Writing]
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.
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.