Project

General

Profile

Actions

Stabilisation process » History » Revision 5

« Previous | Revision 5/8 (diff) | Next »
Greg Burri, 11/06/2009 03:32 PM


Stabilisation process

These process involves during the alpha and beta phases. It consists to try to find and resolved a maximum of bug.

  1. Take a look in the bug list, if there is some of them tagged as Urgent or Critical and you are able to resolve it (you know the component involved) then try to fix them.
    1. Before resolving it, write a unit test into the component test pool if possible to reproduce the bug. The goal is to prevent future regression.
  2. If there is no bug to resolve, play freely with the software, do anything you want, try to use it in the most unconventional way.
  3. If you detect an anomaly :
    1. Try to locate the component and the chunks of code involved
    2. If it's a critical bug and you know the component try to resolve it immediately
    3. Else insert it as a new issue in the bug tracker. Write a maximum of functional and technical details. It's very important to write the way to reproduce it.

Updated by Greg Burri over 14 years ago · 5 revisions