Page Comparison

...

1. we keep the practice of developing on feature branches
2. the master branch holds only code that PASSED QA
   major →  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)
   
3. releases are staged and maintained each on their own branch 
4. release branches are branched off master
5. minor versions are released from the corresponding major release branchbranch 
6. releases are marked with tags of the form 'v<major>.<minor>'
7. 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