Re: [4diac-dev] Suggestion of using git-flow like workflow for developme

[Gerhard Ebenhofer <gerhard@xxxxxxxxxxxxx>]

Hi,

from my point of view it seems to be a good "workflow". As I'm currently not that familiar with the git commands (especially with advanced options like "--no-ff" as mentioned in the articles you linked) - it might be useful to have something like a "cheat-sheet" with the main git commands (and the corresponding UI functionalities in EGit) to be used in the 4DIAC-git-flow workflow.

Do you think it is possible and usefull that we make a "4DIAC - git-flow workflow" cheat sheet?

Regards,

Gerhard

 

On Fri, Mar 4, 2016 at 2:41 PM, Alois Z. <alois.zoitl@xxxxxx> wrote:

Hi,

 

After reading more on git and how to use it I would like to propose a git-flow like workflow [1] to be used for our developments in 4DIAC.

The key point is to use master only for releases and a seperate development branch for the main development. The rest is rather similar how we did it with hg. The reason I'm saying git flow like workflow is that thre is currently no fully functional Eclipse plugin for git-flow and I would strongly recomend to use EGit with Mylin connected to our bugzilla for commiting in 4DIAC.

 

However the most important steps are very good described in this [2] blog post.

 

What do you think?

 

Cheers,

Alois

 

[1] http://yakiloo.com/getting-started-git-flow/

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

_______________________________________________
4diac-dev mailing list
4diac-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/4diac-dev

--

Gerhard Ebenhofer

Am Fundbach 13/4

4501 Neuhofen an der Krems
gerhard@xxxxxxxxxxxxx

+4369912175378