|
|
EffectiveIssuePosting
Good Issue Tracker Posting Habits.
Guidelines For Effectively Reporting Problems To The Issue Tracker.
Before you report a problem to the issue tracker you should:
- search through the issue tracker to see if someone else has reported the problem
- reproduce the problem with the latest version of FDS and Smokeview
- reproduce your problem with a simplified version of your input file.
When you make a report to the issue tracker:
- give your report a meaningful title.
- include the code version and subversion revision number (if you type fds5 or smokeview at a prompt without an input file, this info will be displayed) and the operating system
- provide a summary of your problem including any steps you took to try and solve it.
- attach the simplified version of your input file that reproduces the problem
When you reveive email updates on your report:
- if we request additional information from you, please respond promptly
- once we have fixed your report, please verify the fix once we release a new version
For guidelines on posting to the FDS-Smokeview discussion group effectively, see the Effective Posting Wiki
Sign in to add a comment