Bug Tracker

Bug Response Procedure

We have developed this procedure to enable the fastest recovery to the highest requirements. While we make an effort to repair all bugs, some applications may no longer be open to modification by us. Others may have technical limitations preventing the speedy repair of the issues.

Determine Risk and Impact

Our bug evaluation starts here. Web based scripts with internet vulnerabilities will take precedence over minor application bugs, where as programs that have many downloads will be repaired before one with few.

Our primary goals are in this order: Commercial and Web Applications, Free and Software Applications, Open-Source downloads.

Bug Evaluation Report

Once a bug is deemed valid, dependent on current risks, a BER (Bug Evaluation Report) will be made detailing the issue, any current workarounds, and when a patch should be available.

(For example, a risky bug that isn't well known won't be published with a BER until several workarounds, or a patch can become available. This will minimize risk to our clients.)

Diagnose and Repair / Test

In this stage, we will diagnose any issues with the application, and repair them. We will continue this loop of testing / repairing until the bug is repaired.

Issue Patch and Contact

At this point, we will issue a patch, or an updated package, and E-Mail all of our registered customers. If there was no BER issued in the past, one will be issued at this point.

Attribution

When filling out a bug report, we request your name. This is optional. If a bug is deemed valid, we will attribute the finding of the bug to you. We are a responsible company, and believe that any issue with our software is our issue. By bringing bugs to our attention, no matter how minor, you will be helping everybody who uses our products.