Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Releasing Project Flow

We scheduled the release every Tuesday. The release build contains all the merged PRs (bug fixes/feature implementation) in the week and should be ready on Monday, QA performs tests on the release build to make sure the quality of the build.

  • All PRs (bug fixes or feature implementation) which is scheduled for release should be merged to develop before Monday. Approved/Merged PRs after Monday will be included in the next release.
  • Every PRs should be tested by QA before merging to Develop and Code Freeze.
  • Any issues found during the test should be discussed with the PM to determine if the issue should be fixed in the release or can be included in the next release.

Time estimation

The time estimation for release preparation is 1 week after the demo.

Merging

  1. Essential Output: Merged all approved PR to the develop branch and documented by QA.
  2. Outcomes & Value derived:
    1. QA tests the fixes or implemented features before approving the PR.
    2. Approved PRs are documented by QA, link documentation here.
    3. Approved PRs are merged into develop and the code is frozen (no more code change). If there is any update, QA needs to test it again and re-approve the PR.

Preparation Release

  1. Every merge to master, Mandatory need attach the release checklist, if doesn’t share the release checklist, Please confirm with team lead to completed the release checklist. this is to avoid human error that forgets settings or anything in the production.

Release test

  1. Essential Output: Merged release build has been made and tested by QA.
  2. Outcomes & Value derived:
    1. QA to perform the last test on the merged release build. Test procedures include:
      1. QA General release checklist: here
      2. Smoke test checklist: here
    2. Any issues found during the test should be reported and discussed with PM.
      1. QA to create a ticket for any issues found.
      2. Discuss it with PM, if the issue is not critical, move the issue to the backlog.
      3. If the issue is critical, please do a hotfix.
    3. If the release is approved by PM & DevOps, approve the PR release and the build can be released.