Improve our git workflow; stable releases

[andrew_peterson]

We should probably have parallel branches for stable versus development branches, and should consider just having a regular release schedule (e.g., every second month a new release comes out). See below for some discussions of this

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

https://about.gitlab.com/2015/12/07/why-we-shift-objectives-and-not-release-dates-at-gitlab

[Alireza Khorshidi]

I would suggest creating two branches for now; master branch for tagged versions and develop branch for under development versions.

We could also take a three branch model; master branch for tagged versions, release branch for "near-tagged" versions, and develop branch for under development versions.

Which one would you suggest?

[Alireza Khorshidi]

Thought about.