On Wed, Jun 29, 2011 at 9:34 AM, Blake Johnson <blakejohnso...@gmail.com> wrote: > > The main consequence of using git-flow in our project is that there > would be "master" and "develop" branches stored on GitHub. "Master" > would always represent the latest release version, and we primarily > work in the "develop" branch. The occasional feature branch might also > get pushed to GitHub if several people were working on it at once.
This sounds reasonable to me, but I would make the suggestion that we keep with our prior naming conventions. So the git "master" branch would be the development branch, and a new "makaanga" branch would be where releases come from. I'm also curious how this will interact with our multiple repo and submodule configuration. Owen -- To post to this group, send email to habari-dev@googlegroups.com To unsubscribe from this group, send email to habari-dev-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/habari-dev
