Overview

Steps

[RM] creates new branch release/weekly_DD_MM_YYYY. This branch is created after previous monthly or weekly lands on production. 

• See release branch conventions in “Branching Definitions & Naming Conventions” slide. 

[dev] develops his or her change on Weekly_DEV sandbox

[dev] creates new weekly/* branch from master (see conventions for weekly/* branch in “Branching Definitions & Naming Conventions” slide). 

[dev] creates new pr from the weekly/* branch to the target release branch

[techlead/techlead backup] reviews the Pull Requests and approves if passing 

[RM] creates Weekly_INT validation branch (release/weekly_<DD_MM_YYYY>_weekly_int_validation) (one time work per release)

[RM] merges the release branch into the Weekly_INT validation branch

[RM] coordinates component deployment and unit tests fixing for Weekly_INT

[RM] one the work is validated in Weekly_INT, marks Jira user story as “Ready for UAT” (skipping “Ready to INT” status) and assigns it to the Release Manager, with other required information such as Fix Version.

[RM] creates UAT validation branch (release/weekly_<DD_MM_YYYY>_uat_validation) (one time work per release)

[RM] merges the release branch into the UAT validation branch

[RM] coordinates component deployment and unit tests fixing for UAT

[RM] creates release validation branch for production (release/weekly_<DD_MM_YYYY>_production_validation) (one time work per release)

[RM] coordinates component deployment and unit test fixif for PRD

[RM] merges pthe release branch to master. It trigger the validation again.

[RM] presses the quick deploy and executes post deployment step

The best way to get IT support is to use the new Service One Platform.