Multi-Branched development with Git Source Code Management
1. Multi-Branched Development – System Perspective
PreProdIntegration
QA1
(RTB)
QA2
QA3
Dev
• You develop off your own/team feature branch.
• You then move the feature into a targeted QA branch as designated by the Release Manager.
• When verified, changes would merge into an integration/release branch for testing changes together as a build.
•Testing would be done in the Integration environment.
•After integration testing, the build/release is staged and deployed.
How it works:
Status: QA Testing
Set QA Env
Dev spins off
feature branch
Rel Mgr
approves &
designates QA
Env per project
Dev merges to
release branch.
Status: Int Testing
Prod
Release xyz tagged Release xyz
released by Rel
Mgr.
2. • Everything in QA now will go to QA1 (RTB)
– New projects will go to other designated QA’s
• Development server and Dev branch becomes obsolete (can
be used for prototyping, experimenting).
• Mainline -> release version 1
• SCM will remain running for reference.
Multi-Branched Development – Cutting Over