Project

General

Profile

Stabilisation process » History » Revision 6

Revision 5 (Greg Burri, 11/06/2009 03:32 PM) → Revision 6/8 (Greg Burri, 11/06/2009 03:34 PM)

h1. Stabilisation process 

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

 # 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. 
 ## 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. 
 ## When you commit some patch, don't forget to add the reference to the ticket into the commit message like #42. 
 # 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. 
 # If you detect an anomaly : 
 ## Try to locate the component and the chunks of code involved 
 ## If it's a critical bug and you know the component try to resolve it immediately 
 ## 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.