Deployment To Production Process

Deployment to production process:
1 — we add information to the relevant, release-specific wiki page including new environemt variables and database changes.
2 — we use this to ask DevOps to make sure that the changes listed are applied to the new production deployment.
3 — we create a branch from master calling it the version of the system like 2.3.0.
4 — it goes to UAT with 2 weeks of testing.
5 — if testing finds a bug then we solve it in master and merge it to the branch 2.3.0 by cherry-picking the commits so that we merge to it only the commits that had to do with the bug.
6 — when we think we are ready to release 2.3.0, we tag the branch as 2.3.0-RC-1 at the last commit.
7 — we ask DevOps to do release builds and deploy the version 2.3.0-RC-1 in a new environment and do testing.
8 — if a problem is found then we solve it (see step 5).
9 — we tag the branch 2.3.0 as 2.3.0-RC-2 at the last commit that has the fix we found in step 8.
10-if tests pass then we add another tag next to 2.3.0-RC-2 called 2.3.0-RELEASE.
11-release 2.3.0-RELEASE to production.