Difference between revisions of "IssueReporting"
Jump to navigation
Jump to search
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
LIBISIS is using [http://trac.edgewall.org 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) | LIBISIS is using [http://trac.edgewall.org 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) | ||
| − | * [http://trac.libisis.org/code | + | ==Browsing Issues== |
| + | * [http://trac.libisis.org/code/report/1 Current bugs/issues/tasks] | ||
| + | * [http://trac.libisis.org/code/report Other issue list reports] | ||
| − | ==Issue Priorities== | + | ==Submitting Issues== |
| + | |||
| + | To submit a new issue you need to: | ||
| + | * Go to the [http://trac.libisis.org/code/ main TRAC page] | ||
| + | * Log in with your WIKI username and password | ||
| + | * Click on the "New Ticket" link that will appear in the top menu bar | ||
| + | |||
| + | ===Issue Priorities=== | ||
TRAC defines several priorities for issues and these are our interpretation: | TRAC defines several priorities for issues and these are our interpretation: | ||
Latest revision as of 19:07, 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)
Browsing Issues
Submitting Issues
To submit a new issue you need to:
- Go to the main TRAC page
- Log in with your WIKI username and password
- Click on the "New Ticket" link that will appear in the top menu bar
Issue Priorities
TRAC defines several priorities for issues and these are our interpretation:
| Priority | Interpretation |
|---|---|
| blocker | Unable to use libisis (e.g. DLL fails to load, all procedures crash, installation fails) |
| critical | Most/multiple functions fail to work and give invalid values/crash |
| 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 entered at a higher priority |