Line 44: |
Line 44: |
| 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 | | 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. A good summary should quickly and uniquely identify a bug report. It should explain the problem, not your suggested solution. | + | When reporting a new bug, and after choosing the platform, the next screen asks for more details on your problem. There are 4 main fields that need to be completed. These are '''Component,''' '''Found-In-Version,''' '''Summary,''' and '''Description.''' Fields such as '''Flags''' and '''Requestee''' should be left blank initially by most reporters. The '''CC''' field is for other people you would like notices on this issue to be sent to. YOU will always be automatically included by default, so you don't need to 'cc' yourself. |
| + | |
| + | '''Component:''' As accurately as possible, you may choose which category your issue fits into. If Unknown then choose UNKNOWN. |
| + | |
| + | '''Found-in-version:''' Usually self explanatory. If it applies to more than one version, choose the most recent stable release. |
| + | |
| + | '''Summary:''' How would you describe the bug. BE BRIEF. A good summary should quickly and uniquely identify a bug report. It should explain the problem, not your suggested solution. |
| | | |
| * Good: "Canceling a File Copy dialog crashes File Manager" | | * Good: "Canceling a File Copy dialog crashes File Manager" |
Line 50: |
Line 56: |
| * Bad: "Browser should work with my web site" | | * Bad: "Browser should work with my web site" |
| | | |
− | '''Description:''' The details of your problem report, you may use the following as a template: | + | '''Description:''' Present the details of your problem in this section. You may use the following as a template: |
− | = Environment: | + | '''ENVIRONMENT''': '''''Give a brief server history''''' |
| | | |
| eg. SME Server 7.1, Updated to 7.3 with yum | | eg. SME Server 7.1, Updated to 7.3 with yum |
| | | |
− | = Modifications: | + | '''MODIFICATIONS''': '''''List any contribs or modifications you have on the server''''' |
− |
| |
− | If the following produce any output, attach the results (don't post inline)
| |
− | /sbin/e-smith/audittools/templates
| |
− | /sbin/e-smith/audittools/newrpms
| |
− |
| |
− | or say, no custom-templates or contribs.
| |
| | | |
− | = Original problem: | + | eg. If the following produce any output, attach the results (don't post inline) |
| + | /sbin/e-smith/audittools/templates |
| + | /sbin/e-smith/audittools/newrpms |
| | | |
− | Overview: | + | '''''or say''''', no custom-templates or contribs. |
| | | |
− | Steps to Reproduce: | + | '''ORIGINAL PROBLEM''': '''''State what you were trying to do.''''' |
| + | |
| + | '''STEPS TO REPRODUCE''': '''''As accurately and exactly as possible state what you did to get your problem.''''' |
| | | |
− | Actual Results: | + | '''ACTUAL RESULTS''': '''''List what you got as a result.''''' |
| | | |
− | Expected Results: | + | '''EXPECTED RESULTS''': '''''List what you expected to happen.''''' |
| | | |
| ===Verifying Bugs=== | | ===Verifying Bugs=== |