- we keep the practice of developing on feature branches
- the master branch holds only code that PASSED QA
→ Dev sets task on QA, assigns to Reviewer
→ Reviewer assigns task back to Dev, either: suggesting improvements (status IN PROGRESS) or approving merge (status APPROVED)features and bug fixes are developed on own branches that are branched off master - before a branch is merged into master it has to pass technical QA
- releases are staged and maintained each on the release branch
- releases are marked with tags of the form 'v<major>.<minor>'
- branch
- master is merged into release at the end of a sprint, this sanpshot is deployed to testing for Acceptance Testing
→ suggestions from Acceptance Testing are filed as new JIRA tasks
Drawio baseUrl https://slidewiki.atlassian.net/wiki diagramName SlideWiki Branching Model width 890.5 pageId 12517406 height 521581 revision 67