Changes

If you can help, the developers can concentrate on fixing the bugs.  

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.  

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]]

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 list below with your [[SME_Server_Development_Framework#%20Troubleshooter|Troubleshooter]] hat on.  

* Ask the questions asked by the essay

• Ask the questions asked by the essay  

* Get the information from the reporter, set the bug to NEEDINFO when more information is required 

• Get the information from the reporter  

* Reproduce the issue

• Reproduce the issue  

* CONFIRM the bug or if you can't reproduce it then add a comment that you cannot reproduce. If no-one can reproduce it then RESOLVED-WORKSFORME may be appropriate.

• Confirm the bug or mark it invalid if you can't reproduce it  

* Summarise the issue if the report isn't clear

• Summarise the issue if the report isn't clear  

* 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  

 

The bugs below need triage, they are split up into SME Server 9, SME Server 8 & contribs.

The bugs below need triage, they are split up into SME Server 9, SME Server 8 & contribs.