You guys probably receive a ton of workflow related questions. I'm trying to convert from svn to git. In order to complete, I would like to be able to provide a workflow to our team. We typically go from dev -> qa -> production (Java and Rails projects). The problem is that sometimes QA can get backed up and we'll need to release something to production while QA is doing their thing. What is a good workflow? I would like to not use git-flow, because it's another tool. I've read suggestions to use environment branches (master, staging, production). I've also read not to do this and just use master, tagging your production releases. How well would our setup, where things can get backed up, work with the latter? Are there any alternative suggestions? Thanks, Bradford -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html