[DO NOT MERGE] Proposed implementation plan for automated release workflow#338
Draft
hdamker wants to merge 9 commits intocamaraproject:mainfrom
Draft
[DO NOT MERGE] Proposed implementation plan for automated release workflow#338hdamker wants to merge 9 commits intocamaraproject:mainfrom
hdamker wants to merge 9 commits intocamaraproject:mainfrom
Conversation
hdamker
requested review from
rartych,
soadeyemo and
tanjadegroot
as code owners
This was referenced Nov 25, 2025
Contributor
albertoramosmonagas
left a comment
albertoramosmonagas
left a comment
There was a problem hiding this comment.
A few comments, but everything is fine 👍
documentation/SupportingDocuments/CAMARA-Release-Workflow-Implementation-Plan.md
Show resolved
Hide resolved
documentation/SupportingDocuments/CAMARA-Release-Workflow-Implementation-Plan.md
Outdated
Show resolved
Hide resolved
documentation/SupportingDocuments/CAMARA_Release_Process_coverage_of_fall_25.md
Show resolved
Hide resolved
This commit adds comprehensive documentation proposing the implementation of the CAMARA automated release workflow concept: - CAMARA-Release-Workflow-Implementation-Plan.md: Proposed phased implementation plan with 5 phases from Nov 2025 to Fall 2026, including 20 sub-issues, timeline alignment, and success criteria - CAMARA_Release_Rrocess_coverage_o_fall_25.md: Workflow categories (C1-C5) and topic-by-topic coverage mapping from wiki page Key aspects of the proposed plan: - Phase 1A (Nov-Dec 2025): Metadata schemas and Release Progress Tracker integration with presentation on Dec 10 - Phase 1B (Dec 2025-Jan 2026): Validation framework stable by mid-Jan for Fall26 cycle start - Phase 2 (Jan-Feb 2026): Release automation functional by Spring26 M3 (Jan 31) - Phases 3-5: Full rollout, maintenance workflow, and production hardening through Fall 2026 Related to camaraproject#191
Rationale: - Consistency: Existing tooling (api_review_validator, validate-release-plan) is already Python-based. - Simplicity: Python scripts using standard libraries avoid the overhead of node_modules and build steps for simple local validation tasks. - Suitability: Python is well-suited for the required file I/O, git operations, and semantic version parsing needed for these context-aware checks. - Alignment: Ensures the plan matches the actual implementation direction.
- Renumber phases to 1-7 (Concept, Rollout, Validation, Automation, Ops, Maint, Deferred) - Shift Phase 2 (Rollout) deadline to Jan 15, 2026 - Define Mass Rollout Strategy targeting all ~61 repositories - Add detailed deliverables for automated campaign and minimal validation - Move Wiki Integration to Phase 2 for immediate value - Update issues list camaraproject#191.1-camaraproject#191.18 and dependencies - Manual adjustments to issue placement and estimation logic - Add Table of Contents
Co-authored-by: Alberto Ramos Monagas <alberto.ramosmonagas@telefonica.com>
Clarify certain lists are examples not definitive: - Custom validators (actual list TBD) - Presentation materials (content TBD) - Checklist automation (capabilities TBD) - Success criteria numbers updated to TBD where appropriate
hdamker
force-pushed
the
release-process-implementation-plan
branch
from
e02b7d7 to
68baad7
Compare
- Update Timeline Alignment table with detailed Fall26 milestones (M0-M4) - Fix Success Criteria headers (remove incorrect phase labels) - Update Phase 4 objectives to target Feb 28 for Spring26 M4 - Remove Next Steps section (superseded by GitHub issues)
hdamker
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
[UPDATED] This PR description has been updated to reflect the restructured plan targeting a Mass Rollout strategy by Jan 15, 2026. It's not intended to be merged, but available here for information. Relevant are the issues in ReleaseManagement.
What type of PR is this?
documentation
What this PR does / why we need it:
This PR adds comprehensive documentation proposing the implementation of the CAMARA automated release workflow concept defined in CAMARA-Release-Workflow-and-Metadata-Concept.md.
The implementation plan has been restructured into 7 distinct phases to support a Mass Rollout Strategy:
Key deliverables:
project-administrationtooling.The plan addresses:
Which issue(s) this PR fixes:
Related to #191
Special notes for reviewers:
r3.4) rather than meta-release references.Changelog input
Additional documentation
Includes:
documentation/SupportingDocuments/CAMARA-Release-Workflow-Implementation-Plan.md: Comprehensive phased implementation plandocumentation/SupportingDocuments/CAMARA_Release_Rrocess_coverage_o_fall_25.md: Workflow categories (C1-C5) mapping