release_management
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| release_management [2025/12/30 10:42] – [4.2 Branch Creation Guidelines (Mandatory)] pradnya | release_management [2025/12/30 10:46] (current) – [2.] pradnya | ||
|---|---|---|---|
| Line 11: | Line 11: | ||
| Dev → Main → Test → Production (+ Demo, Hotfix) | Dev → Main → Test → Production (+ Demo, Hotfix) | ||
| - | ===== 2. ===== | + | ===== 2. Release Manager Responsibilities |
| The Release Manager is responsible for: - Ensuring correct branch promotions - Verifying CI/CD status before approvals - Enforcing reviewer and environment protections - Acting as the final gatekeeper for Production deployments | The Release Manager is responsible for: - Ensuring correct branch promotions - Verifying CI/CD status before approvals - Enforcing reviewer and environment protections - Acting as the final gatekeeper for Production deployments | ||
| Line 68: | Line 68: | ||
| Rules: - Always verify the **base branch** before creating a new branch - Branch names must follow the approved naming convention - Do not create long-lived branches other than Dev, Main, Test, Demo, Production | Rules: - Always verify the **base branch** before creating a new branch - Branch names must follow the approved naming convention - Do not create long-lived branches other than Dev, Main, Test, Demo, Production | ||
| - | ==== 4. ==== | + | ==== 4.3 Creating the Demo Branch (One-Time) |
| If the Demo branch does not exist: | If the Demo branch does not exist: | ||
release_management.1767091373.txt.gz · Last modified: by pradnya