**Meeting: 9 Aug. 2018**:

# Channel improvements

## Problem

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.

## Testing

Before each releases every clients MUST past a list of scenarios.

Scenarios are described here:
[testJAMI.ods](uploads/9190692c7b4b73d9d512ec8996568bff/testJAMI.ods)

And are reviewed by QA dpt. before sending it to the developers if needed.

## Special note: FDroid

@pduchemin added a patch on this issue : https://gerrit-ring.savoirfairelinux.com/c/ring-client-android/+/11095
Still need to be tested

## Related issues

+ https://git.ring.cx/savoirfairelinux/ring-project/issues/492
+ https://git.ring.cx/savoirfairelinux/ring-project/issues/493
+ https://git.ring.cx/savoirfairelinux/ring-project/issues/494

See: https://git.ring.cx/savoirfairelinux/ring-project/milestones/1