This document outlines the version control process using branching and tagging. Developers create branches off the master version to work on features independently and merge them back after testing. The master version is then updated and tagged to release the application, with automated builds, tests, and code reviews at each step. Separate versions are maintained through branching for concurrent development and tagging for releases.

1. VERSION CONTROL

2. Master Version 1
Version 1
Dev
Version 1
Dev Clone
Feature A
Feature A
Merge
- Auto Build
- Integration Test
- Coverage Test
- Auto Build
- Integration Test
- Coverage Test
- Release App
- Auto Build
- Integration Test
- Coverage Test
- Keep Latest Version
Version 1
Dev Clone
Feature B
Feature B - Auto Build
- Integration Test
- Coverage Test
- Pull Request
- Review Code & Approval

3. Master Version 2
Version 2
Dev
Version 2
Dev Clone
Feature A
Feature A
Merge
- Auto Build
- Integration Test
- Coverage Test
- Auto Build
- Integration Test
- Coverage Test
- Release App
- Auto Build
- Integration Test
- Coverage Test
- Keep Latest Version
- Auto Build
- Integration Test
- Coverage Test
- Pull Request
- Review Code & Approval
Version 2
Dev Clone
Feature B
Feature B

4. Master
Separate version with branching
Version 1Version 2

5. Master
Version 1
Version 2
Separate version with Tagging