Development How To

This is a document for Taskboard developers that describes development practices. It’s intended to show how do we use Kanban methodology with Git repository.

Repository branches

1. story branches – each story or issue should be developed in it’s own branch. This branch should remain local. If there is a need to share the changes with other developers patches should be used (or pulls between developers’ repositories)
2. dev – development branch is intended for code that is still in progress (not yet checked by Product Owner). If the implementation of story/issue is completed it’s branch should be merged do dev branch.
3. done – this should store only fully completed stories/issues. The stories/issues that where in dev branch and where successfully checked by Product Owner should be merged to done branch.
4. master – we use master branch as a release branch – we merge the dev branch to master when we do a release