Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Status
IN PROGRESS
Stakeholders
Outcome
Due date
Owner
Benjamin Wulff 

Background

 

  1. we keep the practice of developing on feature branches
  2. 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)
  3. releases are staged and maintained each the release branch 
  4. releases are marked with tags of the form 'v<major>.<minor>'
  5. 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


 

 

  • No labels