Manage GIT Branches

[chris2fr]

As a developper, I want to be able to manage the latest code relative to my task in progress in order to be efficient in finding my way around which is better than the current system with a master branch, an architecture branch and issue branches.

[chris2fr]

Master is the main development branch, but there is unfinished work on Architecture. I also started gh_pages branch for the automatic Jekyll creation of http://chris2fr.github.io/redmine_taskjuggler

[awilkins]

Recommend a per-topic branching strategy - master is kept stable, and all changes occur in topic branches. This promotes contributions as pull requests have a clear, stable base (master) to start from and are kept neat and easy to merge.

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

[chris2fr]

Agreed.

Can I also interest you in http://www.burnlog.com ?

Thanks,

Christopher

7 place de l'Eglise - 92260 FONTENAY-AUX-ROSES - FRANCE - (prox. Paris) Mob. +33.7.81.81.18.11 Tel. +33.9.53.33.11.11

2015-06-01 11:33 GMT+02:00 Adrian Wilkins [email protected]:

Recommend a per-topic branching strategy - master is kept stable, and all changes occur in topic branches. This promotes contributions as pull requests have a clear, stable base (master) to start from and are kept neat and easy to merge.

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

— Reply to this email directly or view it on GitHub https://github.com/chris2fr/redmine_taskjuggler/issues/43#issuecomment-107380699 .