02 — Capability · BC-1220.10
Release Planning & Versioning
Decide how versions are numbered, how often the product ships and what makes a build a release candidate, so customers and partners can plan against a predictable rhythm.
- Release Cadence
- Version Policy
- Release Train
In scope
- Version numbering and compatibility policy
- Release calendar and train schedule
- Release candidate criteria and go or no-go
Out of scope
- Roadmap content and feature prioritization (see BC-510)
Realized by · 0
- No product in the catalog yet.
Used in · 1
Build it · 0
- Nothing in the library points here yet.
Decomposes into · 4
- BC-1220.10.10Versioning PolicyDefine how versions are numbered and what a major, minor or patch change promises about compatibility.
- BC-1220.10.20Release SchedulingSet and publish the cadence — continuous, weekly, quarterly — and the cut-off points each train honors.
- BC-1220.10.30Release Readiness ReviewCheck a candidate against test results, open defects, security findings and documentation before it is cleared to ship.
- BC-1220.10.40Long-Term Support BranchingMaintain supported older versions for customers who cannot move at the product's pace, with a stated end-of-support date.