Stabilisation process » History » Version 8
Greg Burri, 07/29/2012 10:00 PM
| 1 | 1 | Greg Burri | h1. Stabilisation process |
|---|---|---|---|
| 2 | |||
| 3 | 8 | Greg Burri | These process is used during the alpha and beta phases. It consists to try to find and resolved a maximum of bug. |
| 4 | 1 | Greg Burri | |
| 5 | 2 | Greg Burri | # 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. |
| 6 | 5 | Greg Burri | ## 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. |
| 7 | 6 | Greg Burri | ## When you commit some patch, don't forget to add the reference to the ticket into the commit message like #42. |
| 8 | 1 | Greg Burri | # 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. |
| 9 | 7 | Greg Burri | # If you detect a defect : |
| 10 | 1 | Greg Burri | ## Try to locate the component and the chunks of code involved |
| 11 | ## If it's a critical bug and you know the component try to resolve it immediately |
||
| 12 | ## 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. |