Pretty cool visualisation of the 'GitHub based' TeamMentor Development+QA+Release workflow

Roman created this nice Visio diagram with out current 'GitHub based' workflow for TeamMentor:

Although this is still a draft, it is already a good representation of how we are using Git's powerful forking/cloning capabilities to implement solid Development + QA + Release workflows.

Roman is also creating simpler versions of this diagram, for:

• the cases where we push a patch on a released version (for example targeted bugs or security fixes)
• the workflow used to manage the multiple TeamMentor's Content repositories

Let me know if you have any ideas or suggestions on how to make this even better :)

One area we still need to do some work (and help), is the automation of some of these steps/workflow. We have figured out the git commands, and now we need to automate their execution.

Related Git/GitHub posts:

• Creating the final TeamMentor with SI Library repository via multiple Git pulls and pushes 
• Adding Tags to TeamMentor Master repository 
• Going back in time using Git's checkout 
• Handling content changes made on hosted site created by Git clone (with auto Git commits and pushes?) 
• The need to create forks/clones for TeamMentor.net website 
• Deploying TeamMentor to AppHarbor (.NET Cloud) using Git push 
• Git and GitHub commands to create and deploy new version of TeamMentor 
• Using a Git Branch to fix a Bug