Bug fix policy
Posted by Duncan Clarke, Last modified by Duncan Clarke on 03 May 2016 05:41 PM

Storman Bug Fix Policy


  • Storman Support will help with workarounds and bug reporting.
  • Critical bugs will generally be fixed in the next maintenance release.
  • Non critical bugs will be scheduled according to a variety of considerations.


Raising a Bug Report 

Storman Support is eager and happy to help verify bugs — we take pride in it! Please open a support request in our support system providing as much information as possible about how to replicate the problem you are experiencing. We will replicate the bug to verify, then lodge the bug report for you. We'll also try to construct workarounds if they're possible. 


How Storman Approaches Bug Fixing 

Maintenance (bug fix) releases come out more frequently than major releases and attempt to target the most critical bugs affecting our customers. The notation for a maintenance release is the final number in the version (ie the 1 in 3.0.1). 

If a bug is critical (production application down or major malfunction causing business revenue loss or high numbers of staff unable to perform their normal functions) then it will be fixed in the next maintenance release provided that:

  • The fix is technically feasible (i.e. it doesn't require a major architectural change).
  • It does not impact the quality or integrity of a product.

For non-critical bugs, the bugs are prioritised according to these factors:

  • How many of our supported configurations are affected by the problem.
  • Whether there is an effective workaround or patch.
  • How difficult the issue is to fix.
  • Whether many bugs in one area can be fixed at one time.

We give high priority consideration to security issues.

When considering the priority of a non-critical bug we try to determine a 'value' score for a bug which takes into account the severity of the bug from the customer's perspective, how prevalent the bug is and whether roadmap features may render the bug obsolete. We combine this with a complexity score (i.e. how difficult the bug is). These two dimensions are used when we choose which bugs to fix, in what order.

(0 vote(s))
Not helpful

Comments (0)