| Milestone | Goal of the Milestone | Description of the Milestone - acceptance criteria |
|---|
| M0 | Declaration of participation in the release, initial scope of the release | - Blueprint proposal represented as a Jira EPIC ticket
- Feature lead assigned to Jira Epic ticket - declaration of participation in the simultaneous release
- The initial version of Increment Blueprint stored on Github/tf-spec/Release folder,
- The blueprint presented, discussed, and approved by related committers
- Release Scope Overview updated accordingly
- The initial version of the Release Plan for the project presented
- Dependencies between projects/components/areas identified
|
|---|
| M1 | Identification of dependencies between modules and new functionalities,
release plan for new functionality | - All dependencies between existing functionality and requested change/feature discussed and agreed by PTL and related approvers (based on Modules/Committers)
- Jira Epic ticket broke down into stories in related Jira project (backlog, plan) - presented and discussed on TWS meeting
- The final version of Blueprints, Release Scope and Release Plans for participating projects discussed and approved by approvers
|
|---|
| M2 | Feature/Functionality technical design freeze | - Technical design fully provided, agreed (documentation on the Confluence/Github/tf-spec available)
- Jira Epic ticket updated with a link to technical design
- Documentation started
- Feature tests started
- Feature/Functionality Freeze - Technical Design approved by relevant approvers (Modules/Committers)
|
|---|
| M3 | API freeze (beta available) | - External API available for beta-tests
- Jira Epic ticket updated with information about API availability (documentation link - tf repo)
- Documentation in progress
- Tests in progress
- API Freeze confirmed by Feature Lead (comment on Jira Epic ticket with repo/commit ID link)
|
|---|
| M4 | Code freeze - only bug fixing allowed | - all functionality and APIs available for testing
- Jira Epic ticket updated with information about final API documentation, executed UI tests documentation
- Documentation provided - confirmed by Documentation project PTL
- Code freeze confirmed by Feature Lead (comment on Jira Epic ticket) - only bug fixing allowed
|
|---|
| RC0 | Release candidates freeze - branch stabilization | - Release candidates agreed, approved, tested
- System tests conducted, quality confirmed by CI/CD PTL
- Final documentation provided, reviewed, approved by Documentation PTL
- Marketing information provided to Marketing Advisory Council
- release branch cut off - branch stabilization from now on
- Release Candidates freeze, confirmed by PTL and TSC
|
|---|
| Deployment | Release deployment | official deployment executed |
|---|