Deciding on a branching strategy?

[VagishVela]

I think we should commit to the "develop" branch, then when we do a release we merge to master then do the release off there. This allows us to have tested code in "master" and development code in "develop".

Also how do you think we should do testing? Do we all test a release before we publish it?

[kapitainsky]

IMHO yes - it should be tested. What about to create “release candidate”?

On 20 Mar 2016, at 13:20, Vagish Vela [email protected] wrote:

I think we should commit to the "develop" branch, then when we do a release we merge to master then do the release off there. This allows us to have tested code in "master" and development code in "develop".

Also how do you think we should do testing? Do we all test a release before we publish it?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub #29

[c-o-m-m-a-n-d-e-r]

yes, i created develop branch for this ... first commit there please

[VagishVela]

@c-o-m-m-a-n-d-e-r I've merged master into development so it should be up to date now.

[c-o-m-m-a-n-d-e-r]

thx...

[VagishVela]

As @kapitainsky suggested I think we should do release candidates. Also maybe do a monthly release (unless we are doing a rapid hotfix for a bug)?