2,569
edits
Changes
Jump to navigation
Jump to search
mLine 1:
Line 1: + + Line 20:
Line 22: − ===Working on Bugs===+ − Please help us to make our software as reliable as possible. Please report possible bugs only via the bug tracker and to encourage others to do the same. − − ====Reporting Bugs==== Line 30:
Line 29: + + Line 61:
Line 62: − ====Verifying Bugs====+ Line 86:
Line 87: − ====General====+ − =====Bug Categories=====+ Line 109:
Line 110: − =====Bug Triage=====+ Line 126:
Line 127: − =====Bug Status=====+ Line 197:
Line 198: − =====Bugzilla flags=====+
re-order
==Bug Tracker==
==Bug Tracker==
Please help us to make our software as reliable as possible. Please report possible bugs only via the bug tracker and to encourage others to do the same.
Find, report and fix bugs here http://bugs.contribs.org
Find, report and fix bugs here http://bugs.contribs.org
Use Control Click to select/deselect from selection sets, if none are selected all are.
Use Control Click to select/deselect from selection sets, if none are selected all are.
===Reporting Bugs===
Please take the time to read
Please take the time to read
[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]
Have you have searched the [http://bugs.contribs.org/query.cgi?format=specific open bugs],
Have you have searched the [http://bugs.contribs.org/query.cgi?format=specific open bugs],
and read the SME Server Manual and FAQ ?
and read the SME Server Manual and FAQ ?
For bugs in SME Server Release, SME Server Future & SME Server Translations the following format is suggested. It's not always appropriate eg. New Feature Requests
'''Summary:''' How would you describe the bug, in approximately 60 or fewer characters?
'''Summary:''' How would you describe the bug, in approximately 60 or fewer characters?
Expected Results:
Expected Results:
===Verifying Bugs===
Bugs in the SME Server Release, SME Server Future & SME Server Translations
Bugs in the SME Server Release, SME Server Future & SME Server Translations
will need to be verified, see http://bugs.contribs.org/show_bug.cgi?id=3727 for a good example,
will need to be verified, see http://bugs.contribs.org/show_bug.cgi?id=3727 for a good example,
Marking VERIFIED.
Marking VERIFIED.
===General===
====Bug Categories====
Bugs are sorted by '''Product''', they should be mostly self explanatory. Future/7.x/8.x may need clarifying.
Bugs are sorted by '''Product''', they should be mostly self explanatory. Future/7.x/8.x may need clarifying.
- current development
- current development
====Bug Triage====
If you can help do these steps, the developers can concentrate on fixing the bugs. <br >
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.
The steps in this list is maybe 90% of the time of most bugs.
* 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
====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]
There is no need to verify a non-fix. Invalid/wontfix bugs can move straight to closed.
There is no need to verify a non-fix. Invalid/wontfix bugs can move straight to closed.
====Bugzilla flags====
These will be obvious to the people they are intended to serve. If you feel
These will be obvious to the people they are intended to serve. If you feel
comfortable setting them based on information contained in the bug or needs
comfortable setting them based on information contained in the bug or needs