Difference between revisions of "IssueReporting"
Jump to navigation
Jump to search
| Line 21: | Line 21: | ||
|- | |- | ||
| minor | | minor | ||
| − | | A particular function/module works incorrectly, but there is either a workaround or the problem does not | + | | A particular function/module works incorrectly, but there is either a workaround or the problem does not occur regularly |
|- | |- | ||
| trivial | | trivial | ||
| Something like a documentaton error that is obviously wrong and so would not cause too much confusion; otherwise it should be eneterd at a higher priority | | Something like a documentaton error that is obviously wrong and so would not cause too much confusion; otherwise it should be eneterd at a higher priority | ||
|} | |} | ||
Revision as of 18:18, 16 January 2007
LIBISIS is using TRAC for problem/issue reporting. You can browse issues without logging on, but to report issues you will need to login using your WIKI username and password (the login notes mentioned for write access to the SubversionServer apply to TRAC login too)
Issue Priorities
TRAC defines several priorities for issues and these are our interpretation:
| Severity | Interpretation |
|---|---|
| blocker | Unable to use libisis (e.g. DLL fails to load, all procedures crash, installation fails) |
| critical | Most things fail to work and give invalid values, crash etc. |
| major | A particular function/module works incorrectly and there is no workaround |
| minor | A particular function/module works incorrectly, but there is either a workaround or the problem does not occur regularly |
| trivial | Something like a documentaton error that is obviously wrong and so would not cause too much confusion; otherwise it should be eneterd at a higher priority |