How Storytell Does Release

All changes except urgent bugfix will go to a staging environment first, be fully QA’ed and then be pushed to production environment through releases
- All code merges will trigger CI/CD for the staging environment (staging.storytell.ai)
There will be two releases a week (one in Tuesday and one in Friday. I have marked time in the Oncall Rotation and Product Release Calendar.
- A New PR will be created for every change in the release.
- The PR description will include all PRs in the past page. It will be the Change Log We use.
  - We created a pipedream workflow to automatically create ChangeLog and it is availiable at https://go.Storytell.ai/auto-cl. So there will be one Release Note for each release
- For QA Process:
  - Oncall is the responsible party for the EQA process. If there is new feature and QA playbook needs to be updated, Oncall person will ping the feautre owner to add tickets.
  - Any bugs found in staging server at this stage will be solved in separate PR to Staging
- Oncall is the person who will send this PR to move change to production environment
  - Commit will not be squashed. We will keep the commit so that people who what bugs are fixed by which commit.
- Oncall person is the one who will merge the PR. This will trigger the CI/CD in the production server.