You might consider something that wraps git up in extra QA/management
layers. For example, have a look at gerrit which is used by Google, amongst
others.

https://code.google.com/p/gerrit/



On Sat, Sep 6, 2014 at 5:28 AM, Eric Kolotyluk <eric.koloty...@gmail.com>
wrote:

>  What sort of workflow do people use with their QA teams?
>
> For example, when a feature branch is ready for testing, do people do a
> pull request to master, development, or to a special test/*branch*? When
> QA have confirmed the feature is good, do they then do a pull request to
> master, release, or somewhere else.
>
> Does anyone know of any good documentation that talks about git workflows
> incorporating a test team?
>
> Cheers, Eric
>
> --
> You received this message because you are subscribed to the Google Groups
> "Git for human beings" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to git-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to