LLDBranching & Release Strategy
v1.2 is unreleased — see v1.1 for the current stable release.
Overview
How branches, pull requests, versions, deployment environments, and hotfixes work across the MCM repository ecosystem.
Branching & Release Strategy
MCM is a polyrepo — every mcm-* repository (mcm-api, mcm-ui, every mcm-module-*, mcm-common-lib, mcm-devops, etc.) is versioned and released independently in Git, but shipped together as one product bundle via mcm-devops. This section is the single source of truth for how branches, pull requests, versions, environments, and hotfixes move through that ecosystem — it applies uniformly to every repo.
Sections
| Page | Covers |
|---|---|
| Branch Model | The three environment branches, feature/fix branches, and where release/<minor> fits in |
| PR Approval Flow | Who approves each promotion and the merge strategy used |
| Versioning | Semver, version.txt, and the lockstep release-cycle bump |
| Deployment Environments | The internal VMs each branch actually deploys to, and how production ships |
| Hotfix / Patch Release Strategy | Patching a shipped version without touching main or disturbing in-progress develop work |