The current problem is that features are not correctly checked before each release and a lot of regressions can be discovered after the release. Moreover, nightly = stable on a lot of platforms (e.g. GNU/Linux)
## What we want to do
+ The **master** branch will be used by *US* (developers) and by *Gerrit* for development purpose.
+ Every **X** days (for example: 3) the master of all projects will be released in a **Nightly** Release. This release will not receive any patch and will only exists **X** days.
+ At the first of each month, a freeze will be done on the **master** branch. Then, we will need to validate every scenarios needed to validate the release. If a test fail, the release process is blocked till not fixed. When tests are ok, the release button is pressed. Then, jenkins add a branch named `yyyy_mm` on any project. If a bug fix is done for an important issue and doesn't change the API, it can be backported in this branch. For now, there will be no overlap between supported releases.
