r4.1

[hdamker]

Release Management r4.1 baseline for Sync26

r4.1 is the public release of the Release Management documents with repository
version 0.5.0.

The release consolidates the automated API release process documentation,
metadata schema artifacts, release progress tracking data, and validation
framework design material that landed after r3.1. It provides the Release
Management repository baseline for API teams preparing Sync26 releases and for
the continued evolution of the r4.x release process.

Key Updates

• Automated release process: release creation, review, publication,
  post-release sync, bot UX, and branch terminology documentation.
• Release metadata: release plan and release metadata schema artifacts with
  examples for API repositories.
• API readiness: updated checklist guidance for validation results, warning
  deferrals, and API description requirements.
• Validation framework reference material: requirements, detailed design,
  design-guide audit, testing-guidelines audit, and Commonalities consumption
  design documents.
• Release progress tracking: repository progress tracker workflow and
  generated progress data.
• Sync26 terminology: updated references from Fall26/Spring27 to
  Sync26/Signal27 where applicable.

Changes since r3.1

Added

• Add the release workflow and metadata foundation, including concept material, release metadata schemas, and release plan schema artifacts by @hdamker in CAMARA Release workflow and metadata concept #275 and Add CAMARA release metadata schemas (Issue #337) #339
• Add the automated release process documentation set, covering release creation, release publication, post-release sync, bot UX, API readiness checklist content, and pointer branch documentation by @hdamker in docs: C2 release creation detailed design for review #362, Draft documentation for the metadata-driven release process #364, docs: workflow-owned Release Issue lifecycle #370, docs: add C3-C4 release publication and post-release design #374, Add API Readiness Checklist content #392, and docs: add release pointer branches to documentation #394
• Add validation framework reference material, including Commonalities consumption and bundling design, requirements, detailed design, design-guide audit, and testing-guidelines audit by @hdamker in docs: add Commonalities consumption and bundling design #436, docs: add validation framework requirements and detailed design #447, and docs: update validation framework design to match v1 implementation #463
• Add release progress tracker workflow and generated progress data by @hdamker in Add Release Progress Tracker caller workflow #391
• Add the automated release process update presentation by @tanjadegroot in Add automated release process presentation #424

Changed

• Refine release lifecycle and readiness documentation for the edit/review split, post-release sync step, CHANGELOG handling, breaking changes handling, validation results, warning deferrals, and API description requirements by @hdamker and @tanjadegroot in docs: restructure release lifecycle (edit/review distinction + post-sync step) #523, Add CAMARA Validation result handling to the API readiness checklist documentation #569, and Add handling of Breaking changes section to lifecycle.md #586
• Update README content for the current Release Management documentation structure by @tanjadegroot in Update readme.md to point to new process documentation #460
• Align naming and branch terminology with Sync26/Signal27, source branch terminology, and release branch naming by @hdamker in fix: add Sync/Signal meta-release names and remove validation script #382, docs: replace Fall26 with Sync26 in documentation #384, Harmonize "base commit" to "source commit" and rename src/rX.Y to source/rX.Y #386, and docs: rename post-release sync branch to pr-to-main/{release_tag} #402
• Maintain release progress tracker data through Release Collector bot updates

Removed

• Remove the unused API review trigger workflow by @hdamker in Remove unused api-review trigger workflow #488

Full Changelog: r3.1...r4.1

---

This discussion was created from the release r4.1.