Can I ask how this provides an advantage to someone stumbling across the project's repo? It sounds like you're basically making 'master' into a tag that only gets updated when a release is made... why not just use the tag instead? -----Original Message----- From: "Blake Johnson" <[email protected]> Sent: Wednesday, June 29, 2011 9:34am To: "habari-dev" <[email protected]> Subject: [habari-dev] Git-flow
I realize that the move to GitHub is still a work in progress, but now that we are using git, I wanted to raise the possibility of also using git-flow. Git-flow is essentially a branching model that nicely organizes feature development, hotfixes, and releases. You can read an overview of the model here: http://nvie.com/posts/a-successful-git-branching-model/ Git-flow is a tool which makes it easy to implement this model. You can see a usage example here: http://jeffkreeftmeijer.com/2010/why-arent-you-using-git-flow/ The git-flow project lives on GitHub: https://github.com/nvie/gitflow 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. Thoughts? --Blake -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-dev -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-dev
