#343 Production websites should be against master only
Closed: Fixed Opened by shaiton.

Hi,

This is only a proposal in order to understand our current process.
Actually, the only way to know against which branch is built a specific website is to read the syncStatic.sh puppet script, which lives on a not open repo.

There are two problems around this:
* One does not know where to push a fix
* Those who know it still push on the wrong branch.. (me, sometimes..)

The current process is useful in order to work on the alpha, beta, or release websites. We work on a specific branch who is going to be live at D-day. But the merge is a pain as both branches are updated. The only good thing is that we don't have to mind about the merge at D-day.

My proposal is to push every websites against master. master would be the production branch on every websites, at every time. We will create working branch like for beta, that would be merged on D-day in master for production.

Should we?

This is one of the 3 major change on the build process, that will lead to an easy maintainable architecture. See #90 and #136.


We will try this new process for the next release, (pushing F19 alpha and later).

We will need to prepare alpha on the f19-alpha branch, merge f19-alpha on master at d-day and push when we want to release it!
Should be alive. Easy.

Oh, I need to update the SOP document.

ticket for docs is #181

Metadata