You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 7
Next »
WIP
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
Milestone | Actors & Actions for next milestone | Timeline | Week Nr |
---|
M0 - meta-release kickoff |
| M0 | 0 |
| Release Management - Prepare meta-release page
Commonalities & ICM - Define scope of release.
- Record scope in dedicated GitHub issue.
- Submit scope for TSC review
- Develop Commonalities & ICM scope through one or more alpha release(s)
- Update release tracker on target meta-release page with each alpha release
- Submit final alpha releases PRs for TSC review:
- If OK: create final alpha releases for Commonalities & ICM
TSC - Review final alpha releases PRs of Commonalities & ICM
| 2 weeks |
|
M1 - Draft Commonalities & ICM |
| M0 + 2 weeks | 2 |
| Commonalities & ICM - Fix bugs raised by users through one or more release-candidates
- Update release tracker on target meta-release page with each release-candidate
- Submit final release-candidates PRs for TSC approval
- If approved:
- Create final release-candidates for Commonalities & ICM
- Prepare public-release PR for Commonalities & ICM for M5
TSC - Approval of final release-candidates PRs of Commonalities & ICM
| 10 weeks |
|
M2 - Final Commonalities & ICM |
| M1 + 10 weeks | 12 |
| API Sub-projects - Define scope of API release.
- Record scope in dedicated GitHub issue.
- Submit scope for TSC review
- Create API release tracker for the API version
- Develop API scope through one or more alpha release(s)
- Update the API release tracker with each alpha release
- Submit final alpha API release PR for TSC review:
- If OK: create final alpha releases for the API
TSC - Review final alpha API release PR
| 8 weeks |
|
M3 - Draft APIs |
| M1 + 8 weeks | 10 |
| 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
| 10 weeks |
|
M4 - Final APIs |
| M3 + 10 weeks | 20 |
| Release Management - For Commonalities and ICM, check that all release assets are available in the public-release PR
- If OK: approve creation of public-release of Commonalities and ICM
- For each API release-candidate, check that all release assets are available in the API public-release PR
- Propose meta-release content to TSC
- TSC meta-release approval
- Publish the meta-release
| 2 weeks |
|
M5 - Meta Release |
| M4 + 2 weeks | 22 |
| Release Management - Review release process and identify areas for improvement.
- Release Retro.
- Get inputs from Sub Projects
- TSC Approval.
| 2 weeks |
|
M6 - Post Release |
| M5 + 2 weeks | 24 |
ORIGINAL
Milestone | Milestone Name | Actions to achieve milestone | Timeline | Week number |
---|
Kickoff - M0 | |
| M0 | 0 |
M1 | Initiate Commonalities & ICM | - 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.
| M0 + 2 week | 2 |
M2 | Finalize Commonalities & ICM | - Create release-candidate for Commonalities & ICM
- Prepare public-release for Commonalities & ICM.
- Complete initial PR reviews.
- TSC Approval.
| M1 + 10 weeks | 12 |
M3 | | - Scope Request to Sub-Projects / APIs.
- Determine requirements 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 | 10 |
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 | 20 |
M5 | Meta Release | - Determine the acceptance of the release-candidates for inclusion in the meta-release
- Bundle & publish meta-release
- TSC Approval
- Publish meta-release
| M4 + 2 weeks | 22 |
M6 | | - Review release process and identify areas for improvement.
- Release Retro.
- TSC Approval.
| M5 + 2 weeks | 24 |
Insert separate milestone lines
Milestone | Milestone Name | Actions to achieve next milestone | Timeline | Week number |
---|
Kickoff - M0 | Start of release cycle. |
| M0 | 0 |
|
| - 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.
| 2 weeks |
|
M1 | Initiate Commonalities & ICM |
| M0 + 2 weeks | 2 |
|
| - Create release-candidate for Commonalities & ICM
- Prepare public-release for Commonalities & ICM.
- Complete initial PR reviews.
- TSC Approval.
| 10 weeks |
|
M2 | Finalize Commonalities & ICM |
| M1 + 10 weeks | 12 |
|
| - 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.
| 8 weeks |
|
M3 | Initiate Sub-projects / APIs |
| M1 + 8 weeks | 10 |
|
| - 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
| 10 weeks |
|
M4 | Finalize Sub-projects / APIs |
| M3 + 10 weeks | 20 |
|
| - Determine the acceptance of the release-candidates for inclusion in the meta-release
- Bundle & publish meta-release
- TSC Approval
- Publish meta-release
| 2 weeks |
|
M5 | Meta Release |
| M4 + 2 weeks | 22 |
|
| - Review release process and identify areas for improvement.
- Release Retro.
- TSC Approval.
| 2 weeks |
|
M6 | Post- Release |
| M5 + 2 weeks | 24 |
separate action in 2 columns (but would need a 3rd for RM actions)
Milestone | Milestone Name | Actions Commonalities & ICM | Actions API Sub-projects | Timeline | Week Nr |
---|
Kickoff - M0 | Start of meta-release |
|
| M0 | 0 |
|
| - 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.
|
| 2 weeks |
|
M1 | Initial Commonalities & ICM |
|
| M0 + 2 weeks | 2 |
|
| - Create release-candidate for Commonalities & ICM
- Prepare public-release for Commonalities & ICM.
- Complete initial PR reviews.
- TSC Approval.
|
| 10 weeks |
|
M2 | Final Commonalities & ICM |
|
| M1 + 10 weeks | 12 |
|
|
| - 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.
| 8 weeks |
|
M3 | Initial Sub-projects / APIs |
|
| M1 + 8 weeks | 10 |
|
|
| - 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
| 10 weeks |
|
M4 | Final Sub-projects / APIs |
|
| M3 + 10 weeks | 20 |
|
|
| - Determine the acceptance of the release-candidates for inclusion in the meta-release
- Bundle & publish meta-release
- TSC Approval
- Publish meta-release
| 2 weeks |
|
M5 | Meta Release |
|
| M4 + 2 weeks | 22 |
|
| - Review release process and identify areas for improvement.
- Release Retro.
- TSC Approval.
|
| 2 weeks |
|
M6 | Post Release |
|
| M5 + 2 weeks | 24 |
merge milestone and milestone name columns
Milestone | Actions Commonalities & ICM | Actions API Sub-projects | Timeline | Week Nr |
---|
M0 - meta-release kickoff |
|
| M0 | 0 |
| - 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.
|
| 2 weeks |
|
M1 - Initial Commonalities & ICM |
|
| M0 + 2 weeks | 2 |
| - Create release-candidate for Commonalities & ICM
- Prepare public-release for Commonalities & ICM.
- Complete initial PR reviews.
- TSC Approval.
|
| 10 weeks |
|
M2 - Final Commonalities & ICM |
|
| M1 + 10 weeks | 12 |
|
| - 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.
| 8 weeks |
|
M3 - Initial Sub-projects / APIs |
|
| M1 + 8 weeks | 10 |
|
| - 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
| 10 weeks |
|
M4 - Final Sub-projects / APIs |
|
| M3 + 10 weeks | 20 |
|
| - Determine the acceptance of the release-candidates for inclusion in the meta-release
- Bundle & publish meta-release
- TSC Approval
- Publish meta-release
| 2 weeks |
|
M5 - Meta Release |
|
| M4 + 2 weeks | 22 |
| - Review release process and identify areas for improvement.
- Release Retro.
- TSC Approval.
|
| 2 weeks |
|
M6 - Post Release |
|
| M5 + 2 weeks | 24 |