334
edits
Changes
Jump to navigation
Jump to search
Created page with "{{note box| Please help us to triage all open bugs for SME Server. The steps involved in triage are pretty straightforward and easy to do. Please see the [[SME_Server:Document..."
{{note box| Please help us to triage all open bugs for SME Server. The steps involved in triage are pretty straightforward and easy to do. Please see the [[SME_Server:Documentation:QA#Reporting_a_bug|Bug Triage]] page.}}
If you can help, the developers can concentrate on fixing the bugs.
The steps in this list take approx 90% of the time in the resolving 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.
• Go into triage mode this page can help You : Bugzilla_Reports
• Ask the questions asked by the essay
• Get the information from the reporter
• Reproduce the issue
• Confirm the bug or mark it invalid if you can't reproduce it
• Summarise the issue if the report isn't clear
• 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
The bugs below need triage, they are split up into SME Server 9, SME Server 8 & contribs.
== SME Server 9 ==
{{#bugzilla:columns=id,status,summary
|product=SME Server 9.X
|status=UNCONFIRMED,NEEDINFO
|sort=id
|noresultsmessage="Well done guys, no more open bugs!"}}
== SME Server 8 ==
{{#bugzilla:columns=id,status,summary
|product=SME Server 8.X
|status=UNCONFIRMED,NEEDINFO
|sort=id
|noresultsmessage="Well done guys, no more open bugs!"}}
== SME Server Contribs ==
{{#bugzilla:columns=id,status,summary
|product=SME Contribs
|status=UNCONFIRMED,NEEDINFO
|sort=id
|noresultsmessage="Well done guys, no more open bugs!"}}
[[Category:SME Server Development Framework]]
[[Category:SME9-Development]]
If you can help, the developers can concentrate on fixing the bugs.
The steps in this list take approx 90% of the time in the resolving 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.
• Go into triage mode this page can help You : Bugzilla_Reports
• Ask the questions asked by the essay
• Get the information from the reporter
• Reproduce the issue
• Confirm the bug or mark it invalid if you can't reproduce it
• Summarise the issue if the report isn't clear
• 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
The bugs below need triage, they are split up into SME Server 9, SME Server 8 & contribs.
== SME Server 9 ==
{{#bugzilla:columns=id,status,summary
|product=SME Server 9.X
|status=UNCONFIRMED,NEEDINFO
|sort=id
|noresultsmessage="Well done guys, no more open bugs!"}}
== SME Server 8 ==
{{#bugzilla:columns=id,status,summary
|product=SME Server 8.X
|status=UNCONFIRMED,NEEDINFO
|sort=id
|noresultsmessage="Well done guys, no more open bugs!"}}
== SME Server Contribs ==
{{#bugzilla:columns=id,status,summary
|product=SME Contribs
|status=UNCONFIRMED,NEEDINFO
|sort=id
|noresultsmessage="Well done guys, no more open bugs!"}}
[[Category:SME Server Development Framework]]
[[Category:SME9-Development]]