H.11.3 Release Identity
recommendedReading progress1 missing
Prerequisites0/1 complete
Articles read
1 required article is still unread. Reading it first is recommended, but not required.
Article in preparation — showing conspect notes
A release identity names a product candidate or supported release; some version schemes also promise compatibility.
- Internal identifiers may derive from commit, CI sequence, or release train when they map unambiguously to artifacts.
- Use SemVer or an ecosystem-specific scheme only when consumers rely on its compatibility meaning.
- Calendar, train, and commit-derived identifiers are valid local choices, not universal monorepo formats.
- Map every release identifier to source, artifacts, configuration, tools, provenance, and approval.
- Keep automated version calculation separate from authority to approve or promote a release.