Creating a new bug description
Choose a severity: low, medium, high. The following are rough guidelines:
High: something broken in one of the core parts of Ticc.
Medium: something does not work well in the core Ticc, or something is broken in a non-core portion of Ticc.
Low: anything less serious than the above.
Fill in a short title (the title is arbitrary), and click on a Create button; fill in the template. Everything above the ---- will be shown in the summary page. It may be best that you follow closely the template above the ----.
Priority
Within a severity section, the star symbols are used to denote priority (use {*} and {o} ). The scale is:
Critical: we must fix it before continuing with other work.
Better fix it very soon.
We should work on it.
Dormant. Let's not work on it, at least for now.
Smileys can be used to convey informal information.
Attachments
Upload as attachments any useful input and output. In particular, upload .in and .si files that enable us to reproduce the bug. Attach also any relevant output. We discourage you however from attaching huge files(tens of MB): they are slow to download, and a user is probably interested in only a small portion of them.
Managing bug descriptions
To change a bug description, simply click on the edit link.
- You can change star ratings, and smileys, as appropriate.
To change severity, you need to rename the page, using Ticc/BugLow, Ticc/BugMedium, and Ticc/BugHigh as appropriate.
To close a bug, rename it, changing the portion before the / to Ticc/BugClosed.
Dvlab Open Wiki