Overview

Steps

[RM] creates new branch release/bugfix_<DD_MM_YYYY>_<build>. 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 Bugfix sandbox

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

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

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

[RM] creates UAT Bugfix validation branch (release/bugfix_<DD_MM_YYYY>_<build>_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 (only if required to be run) for UAT

[RM] creates release validation branch for production (release/bugfix_<DD_MM_YYYY>_<build>_<environment>_validation) (one time work per release)

[RM] coordinates component deployment and unit tests (if required) for PROD

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

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