WIP
Table of Contents |
---|
UPDATE PROPOSAL
Release Milestones
Release milestones and their associated tasks, are used to track the status of the meta-release. The milestones and management tasks used in the release process are described in the table below.
LATEST (back to 1 column for actions) add actor and split groups of actions per actore
...
TO BE ARCHIVED
Review closed (2024-04-30) - approved content move to Meta-release Milestones page. - this page is kept to resolve comments and will be archived.
UPDATED PROPOSAL FOR REVIEW (2024-04-23)
Please review the table on this page - proposal is that it replaces the table on the Meta-release Milestones page.
Milestone / start date | Actors & Actions for next milestone | Timeline | Week Nr |
---|---|---|---|
pre-M0 | Release Management
Commonalities & ICM (from previous M2)
TSC
| ||
M0 | Meta-release kickoff | M0 | 0 |
starts @ M0 | Release Management |
Commonalities & ICM
|
|
|
|
|
|
TSC |
|
| 2 weeks | |
M1 |
Alpha Commonalities & ICM | M0 + 2 weeks | 2 | |
starts @ M1 | Commonalities & ICM
|
|
|
|
|
|
|
|
Release Management
TSC |
|
|
7 weeks | |
M2 | Release- |
candidate Commonalities & ICM | M1 + |
7 weeks | 9 |
starts @ M1 | API Sub-projects
|
|
|
...
M3
...
M1 + 8 weeks
...
- Conduct testing and log test result.
- Evaluate and log acceptance criteria.
- Code Freeze
- Create release-candidate for Sub-Projects / APIs.
- Prepare public-release for Sub-Projects / APIs.
- Request approval of Sub-projects / APIs to Release Management WG for meta-release
...
M4
...
M3 + 10 weeks
...
- Determine the acceptance of the release-candidates for inclusion in the meta-release
- Bundle & publish meta-release
- TSC Approval
- Publish meta-release
...
M5
...
- Review release process and identify areas for improvement.
- Release Retro.
- Inputs from Sub Projects
- TSC Approval.
...
M6
...
separate action in 2 columns (but would need a 3rd for RM actions)
...
Actions Commonalities & ICM
...
Actions API Sub-projects
...
Timeline
...
Week Nr
...
- Scope of Work Products clarified and recorded in dedicated issue.
- Identify commonalities work products.
- Create alpha release for Commonalities & ICM
- Create initial PRs for commonalities.
- Agree on the scope of commonalities.
- TSC review.
...
M1
...
- Create release-candidate for Commonalities & ICM
- Prepare public-release for Commonalities & ICM.
- Complete initial PR reviews.
- TSC Approval.
...
M2
...
- Scope Request to Sub-Projects / APIs.
- Determine requirements for Sub-projects / APIs.
- Create PRs for Sub-projects / APIs.
- Review and finalize PRs.
- Confirm scope of Sub-projects / APIs
- Define API test cases.
- Define acceptance criteria.
- Create alpha release for for Sub-projects / APIs.
...
M3
...
M1 + 8 weeks
...
- Conduct testing and log test result.
- Evaluate and log acceptance criteria.
- Code Freeze
- Create release-candidate for Sub-Projects / APIs.
- Prepare public-release for Sub-Projects / APIs.
- Request approval of Sub-projects / APIs to Release Management WG for meta-release
...
M4
...
M3 + 10 weeks
...
- Determine the acceptance of the release-candidates for inclusion in the meta-release
- Bundle & publish meta-release
- TSC Approval
- Publish meta-release
...
M5
...
- Review release process and identify areas for improvement.
- Release Retro.
- Inputs from Sub Projects
- TSC Approval.
...
M6
...
merge milestone and milestone name columns
Actions Commonalities & ICM
Actions API Sub-projects
Timeline
Week Nr
- Scope of Work Products clarified and recorded in dedicated issue.
- Identify commonalities work products.
- Create alpha release for Commonalities & ICM
- Create initial PRs for commonalities.
- Agree on the scope of commonalities.
- TSC review.
M1 - Initial Commonalities & ICM
- Create release-candidate for Commonalities & ICM
- Prepare public-release for Commonalities & ICM.
- Complete initial PR reviews.
- TSC Approval.
M2 - Final Commonalities & ICM
- Scope Request to Sub-Projects / APIs.
- Determine requirements for Sub-projects / APIs.
- Create PRs for Sub-projects / APIs.
- Review and finalize PRs.
- Confirm scope of Sub-projects / APIs
- Define API test cases.
- Define acceptance criteria.
- Create alpha release for for Sub-projects / APIs.
M3 - Initial Sub-projects / APIs
M1 + 8 weeks
- Conduct testing and log test result.
- Evaluate and log acceptance criteria.
- Code Freeze
- Create release-candidate for Sub-Projects / APIs.
- Prepare public-release for Sub-Projects / APIs.
- Request approval of Sub-projects / APIs to Release Management WG for meta-release
M4 - Final Sub-projects / APIs
M3 + 10 weeks
- Determine the acceptance of the release-candidates for inclusion in the meta-release
- Bundle & publish meta-release
- TSC Approval
- Publish meta-release
M5 - Meta Release
- Review release process and identify areas for improvement.
- Release Retro.
- Inputs from Sub Projects
- TSC Approval.
|
TSC
- Review final alpha release of the API
M3 - Draft APIs
M1 + 8 weeks
API Sub-projects
- Fix bugs raised by API testers through one or more release-candidates
- Update API release tracker with each release-candidate
- Submit final API release-candidates PR for TSC approval
- If approved:
- Create final API release-candidate
- Prepare API public-release PR for M5
TSC
- Approval of final API release-candidate PR
M4 - Final APIs
M3 + 10 weeks
Release Management
- For Commonalities and ICM, check that all release assets are available for acceptance in the meta-release
- For each API release-candidate, check that all release assets are available for acceptance in the meta-release
- Get TSC approval
- Publish the meta-release
M5 - Meta Release
Release Management
- Review release process and identify areas for improvement.
- Release Retro.
- Get inputs from Sub Projects
- TSC Approval.
M6 - Post Release
ORIGINAL
...
Timeline
...
Week number
...
M1
...
- Scope of Work Products clarified and recorded in dedicated issue.
- Identify commonalities work products.
- Create alpha release for Commonalities & ICM
- Create initial PRs for commonalities.
- Agree on the scope of commonalities.
- TSC review.
...
M2
...
- Create release-candidate for Commonalities & ICM
- Prepare public-release for Commonalities & ICM.
- Complete initial PR reviews.
- TSC Approval.
...
M3
...
- Scope Request to Sub-Projects / APIs.
- Determine requirements for Sub-projects / APIs.
- Create PRs for Sub-projects / APIs.
- Review and finalize PRs.
- Confirm scope of Sub-projects / APIs
- Define API test cases.
- Define acceptance criteria.
- Create alpha release for for Sub-projects / APIs.
...
M1 + 8 weeks
...
M4
...
- Conduct testing and log test result.
- Evaluate and log acceptance criteria.
- Code Freeze
- Create release-candidate for Sub-Projects / APIs.
- Prepare public-release for Sub-Projects / APIs.
- Request approval of Sub-projects / APIs to Release Management WG for meta-release
...
M3 + 10 weeks
...
M5
...
- Determine the acceptance of the release-candidates for inclusion in the meta-release
- Bundle & publish meta-release
- TSC Approval
- Publish meta-release
...
M6
...
- Review release process and identify areas for improvement.
- Release Retro.
- Inputs from Sub Projects
- TSC Approval.
...
Insert separate milestone lines
...
Timeline
...
Week number
...
- Scope of Work Products clarified and recorded in dedicated issue.
- Identify commonalities work products.
- Create alpha release for Commonalities & ICM
- Create initial PRs for commonalities.
- Agree on the scope of commonalities.
- TSC review.
...
M1
...
- Create release-candidate for Commonalities & ICM
- Prepare public-release for Commonalities & ICM.
- Complete initial PR reviews.
- TSC Approval.
...
M2
...
- Scope Request to Sub-Projects / APIs.
- Determine requirements for Sub-projects / APIs.
- Create PRs for Sub-projects / APIs.
- Review and finalize PRs.
- Confirm scope of Sub-projects / APIs
- Define API test cases.
- Define acceptance criteria.
- Create alpha release for for Sub-projects / APIs.
...
Release Management, for each API
TSC
| 9 weeks | ||
M3 | Release-candidate APIs (Code Freeze) | M1 + 9 weeks | 9 |
starts @ M3 | API Sub-projects
Release Management
TSC
| 9 weeks | |
M4 | Public-release APIs | M3 + 9 weeks | 18 |
starts @ public-release PR for an API | Release Management
TSC:
| 2 weeks | |
M5 | Meta-release | M4 + 2 weeks | 20 |
starts @ M5 | Release Management
TSC
| 2 weeks | |
M6 | Post Release Assessment | M5 + 2 weeks | 24 |