Overview

New Flow figure will be updated soon:

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

Note

• At this time, we do not create a release branch for minor releases.
• The RM team deploys minor updates on an as-needed basis. We do not use a single consolidated feature branch; for example, if there are five stories, each change is validated through its own merge request and deployed independently. This is aligned with our current deployment cadence.

Minor / Bugfix process

• [dev] Develops the change in the minor sandbox.
• [dev] Creates a minor/* branch from master (per “Branching Definitions & Naming Conventions”).
• [dev] Creates an MR from minor/* to the target env/uat branch.
• [Tech Lead / Tech Lead backup] Reviews and approves the MR if it meets the required checks.
• [dev] Updates the Jira user story to “Ready for UAT” (skipping “Ready for INT”), assigns it to the Release Manager, and provides required details (e.g., Fix Version).
• [RM] After successful validation of the MR, merges the minor/* branch into the UAT branch.
• [RM] Coordinates component deployment and supports resolution of unit test issues in UAT.
• [RM] Updates the Jira status to “IN UAT” and assigns the Jira items to the testing team.
• [PO] After successful UAT testing, updates the Jira user story to “Ready for Release”,

...

• assigns it to the Release Manager,

...

• and provides required details (e.g., Fix Version).
• [

...

[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.

...

• dev] Creates an MR from minor/* to the target master branch.
• [RM] After successful validation of the MR, merges the minor/* branch into master.
• [RM] Coordinates component deployment and supports resolution of unit test issues in PRD.
• [RM] Updates the Jira status to “Released” and assigns the Jira items to the testing team.