Line 70: |
Line 70: |
| ===Bug and New Feature Verification=== | | ===Bug and New Feature Verification=== |
| [[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]] |
− | If you find a bug you can work on, eg updating information on the wiki, do so. | + | 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. | | There are likely to be a lot of these as they were generated before the wiki was in place. |
| | | |
− | In this example of adding documentation, after you have updated the wiki, return to the bug | + | In this example of adding documentation, |
− | post brief details of the fix, and how to verify it, eg 'updated wiki re: passwords' and give the URL | + | * find a bug where you understand the problem resolved |
− | then change the Status to 'Resolved - Fixed'. | + | * update the wiki, information will go in a manual, be added to the FAQ or a howto, or create a new howto |
| + | * return to the bug post brief details of the fix, and how to verify it, eg 'updated wiki re: passwords' and give the URL |
| + | * then change the Status to 'Resolved - Fixed'. |
| + | * let someone else verify, or verify someone else's work |
| + | |
| + | At the appropriate stage change the Status to 'Resolved - Fixed' or 'Resolved - Verified' |
| | | |
− | Someone else can then review your changes and change the Status from 'Resolved - Fixed' to Verified and the bug is finished.
| |
| Bug Tracker Administrators Close bugs in SME Current or SME Future, but the reporter or maintainer can close in other sections. | | Bug Tracker Administrators Close bugs in SME Current or SME Future, but the reporter or maintainer can close in other sections. |