Topic: Bug Report Rules

Hi fellow shadowcircle users,
In order to keep this section relativelly clean, please observe the following rules:

  1. Before posting please ensure that the bug has not already been reported by someone else. use the forum search function extensively to be sure.

  2. Read rule #1 again and once perfectly assimilated, jump to rule #3 ;-)

  3. Make a complete description of the issue with the following format:

==== Topic subject ====

[BUG_SEVERITY*][SHORT_BUG_DESCRITPION]

* use the same levels than in the body section

==== body ====

Bug Severity:  BLOCKER| CRITICAL | MAJOR [ NORMAL | MINOR

Qualify the bug severity with the following keywords:

BLOCKER: completely crashes the system. Freezes, Kernel Panics, ect...
No workarround is available for the issue yet.

CRITICAL: completely crashes the system. Freezes, Kernel Panics, ect...
A workarround can be used to overcome the issue.

MAJOR: failure making the system or applications difficult to use.
No workarround is available for the issue yet.

NORMAL: failure making the system or applications difficult to use.
A workarround can be used to overcome the issue.

MINOR: issue that have a small impact on the system's behaviour.


Shadowcircle release number: major + minor, plase specify if release candidate or Beta.

Symptoms: Describe what is happening when the bug occurs and the system state with as much details
as possible.

Reproductibility: ALWAYS | OFTEN | OCCASIONALLY | RARE

initial conditions: precisely describe the system state (running processes, opened windows, ect...) before the bug occurence.

Reproduction Procedure: describe the full process to go from initial condictions to the bug triggering, still with as
much details as possible.

Additional Debug Informations (optional):

   -system or application logs
   -backtraces
   -core dumps (keep them small please !! ie gzip'em)
   -In case of hardware related problems, a full copy of dmesg + lspci.

Workarround description (if any)

Patch (if any)