Changes

Changes

863 bytes added , 11:37, 13 April 2007

Line 65: Line 65:

# What happened?

# What do the logs say?

===Bug triage===

EVERYONE reporting bugs needs to read: "How to report bugs effectively":

http://www.chiark.greenend.org.uk/~sgtatham/bugs.html

Once you've done so (read it again, now), look at the bug reports in

Bugzilla with your developer hat on.

Go into triage mode

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

If the people on this DEVELOPMENT list could do these steps, the

developers could concentrate on fixing the bugs. The list above is maybe

90% of the time of most bugs. There are hundreds of people on this list

and less than 10 active developers. You can make them seem like 900

active developers if you pitch in and do the first 90% of the work.

===Bug and New Feature Verification===

If you find a bug you can work on, please do so.

−

As an example, the documentation section, only requires you to take the answer determined in the bug and copy the information onto the wiki.

There are likely to be a lot of these as they were generated before the wiki was in place.

Line 81: Line 106:

At the appropriate stage change the Status to 'Resolved - Fixed' or 'Resolved - Verified'

−

~~Bug Tracker Administrators Close bugs in SME Current or SME Future, but the reporter or maintainer can close in other sections.~~

−

===Bug Status===

2,569

edits

Bugzilla Help (view source)