| 134 | | 2. pennmush-bugs@pennmush.org is the bug reporting address |
|---|
| 135 | | for the PennMUSH developers (suggestions go to pennmush-developers, |
|---|
| 136 | | bugs to pennmush-bugs). This will generally give you the fastest |
|---|
| 137 | | response and is ideal for unusual bugs. A web-based submission |
|---|
| 138 | | form is at http://www.pennmush.org/jitterbug/pennmush |
|---|
| 139 | | |
|---|
| 140 | | When reporting a problem, please always include the following |
|---|
| 141 | | information: |
|---|
| 142 | | |
|---|
| 143 | | 1. PennMUSH version number |
|---|
| 144 | | 2. The type of machine you are using (Sun SparcStation, IBM RS/6000, etc.) |
|---|
| 145 | | 3. The operating system and version (SunOS 4.1.2, AIX 3.2.4, etc.), |
|---|
| 146 | | 4. The compiler and compiler version (gcc 2.4.5, SGI cc 2.10, etc. -- the |
|---|
| 147 | | 'file' command usually tells you the compiler version, if there's no |
|---|
| 148 | | built-in option like '-v' or '-V' to give it), |
|---|
| 149 | | 5. Whether or not you have made any changes to the code. |
|---|
| 150 | | |
|---|
| 151 | | If the problem resulted in a crash and a core dump, a stack trace of |
|---|
| 152 | | the core dump (see the section above) should also be included. |
|---|
| 153 | | |
|---|
| 154 | | If I need additional stuff (like a log of the Configure or make), I'll |
|---|
| 155 | | ask for it, but if you know that it's relevant, you can send it along, |
|---|
| 156 | | too. |
|---|
| | 135 | 2. The PennMUSH bug-tracking site is http://dev.pennmush.org/ |
|---|
| | 136 | To file a new report, click on the 'New Ticket' link. If |
|---|
| | 137 | you want to get emails about updates to the bug report, put your |
|---|
| | 138 | email address in the appropriate field. For 'type', please select |
|---|
| | 139 | the most appropriate category: Bug, suggested feature, documetation |
|---|
| | 140 | issue, build/compliation problems, etc. Be sure to include what version |
|---|
| | 141 | of PennMUSH you found the problem on. |
|---|
| | 142 | |
|---|
| | 143 | If the problem resulted in a crash and a core dump, a stack trace of |
|---|
| | 144 | the core dump (see the section above) should also be included. |
|---|
| | 145 | |
|---|
| | 146 | If we need additional stuff (like a log of the Configure or make), we'll |
|---|
| | 147 | ask for it, but if you know that it's relevant, you can send it along, |
|---|
| | 148 | too. |
|---|
| | 149 | |
|---|
| | 150 | You can also search to see if anyone else has already reported the issue,' |
|---|
| | 151 | see what issues have been fixed for upcoming releases, and much more at |
|---|
| | 152 | the site. |
|---|
| | 153 | |
|---|
| | 154 | The old way of emailing pennmush-bugs@pennmush.org still works, but using |
|---|
| | 155 | the web interface allows you to specifically give an issue type when |
|---|
| | 156 | reporting something. |
|---|
