Switch QUDA to 'git flow' development model?

[mathiaswagner]

We had some discussions at the QUDA workshop at FNAL about the QUDA development model. A quite nice model is 'git flow', see e.g.

http://nvie.com/posts/a-successful-git-branching-model/

and

https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow

Basically it introduces some conventions on how branches are used. Quick summary:

• master is the current stable release
• release branches to prepare a release
• develop is the current development branch (i.e. what quda-0.7 had been)
• features are developed in feature branches that start off from level
• hot fixes are developed in feature branches

A lot of these had been used anyway in QUDA although in a less organized fashion.

The conventions are not terribly hard to follow and there are even tools to support this workflow (from the command line https://github.com/nvie/gitflow but also integrated into GUIs like SourceTree). The use of things like pull requests should be independent of this model.

The upcoming release of 0.7 might be a good time to start with this - if we want to.

At FNAL I had the impression that nobody objected but maybe with a bit more time to look at the articles linked above describing the model we can decide on that.

Even if you don't want to comment in detail a short yes or no feedback is appreciated.

[mathiaswagner]

Closing this as we started that after the 0.7 release.