Branching strategies

[aassuied-ps]

Hi,

I open this discussion following to last week's meeting.

Here's a first proposal for a repository dedicated to one single study. The idea is to have one principal branch for each milestone (no main).
Since some activities can be common to several milestones, it is possible to open two merge requests for a same issue/sub-branch. Lock the branch to end a milestone for a read-only access.