...
Release milestones and their associated tasks, are used to track the status of the release. The milestones and management tasks used in the release process are described in the table below.
| Milestone | Description | Timeline |
|---|
| Kickoff - M0 | Start of release cycle. | M0 |
| Initiate Commonalities & ICM - M1 | Scope of Work Products clarified. |
| M0 + 1 week | ||
| - Identify commonalities among work products. | ||
| - Gather requirements for commonalities. | ||
| - Create initial PRs for commonalities. | ||
| - Complete initial PR reviews. | ||
| - Agree on the scope of commonalities. | ||
| - Select release candidates for commonalities. | ||
| TSC Approval. | ||
| Finalize Commonalities & ICM - M2 | Release of Commonalities. | M1 + 4 weeks |
| TSC Approval. | ||
| Initiate Sub-Projects / APIs - M3 | Scope Request to Sub-Projects / APIs. | M1 + 6 weeks |
| - Determine requirements for sub-projects/APIs. | ||
| - Create PRs for sub-projects/APIs. | ||
| - Review and finalize PRs. | ||
| - Confirm scope of sub-projects/APIs. | ||
| - Identify release candidates for sub-projects/APIs. | ||
| Finalize Sub-projects / APIs - M4 | Release of Sub-Projects / APIs. | M3 + 2 weeks |
| Meta Release | Testing & Acceptance. | M4 + 8 weeks |
| - Conduct testing. | ||
| - Evaluate acceptance criteria. | ||
| Release Retro. | ||
| - Review release process and identify areas for improvement. | ||
| TSC Approval. | ||
| Bundle & publish release |
.....................................
- Work products needed:
- Commonalities
- API-design-guidelines.md
- Camara_Versioning_Guidelines.md
- Glossary.md
- Linting rules (representing the guidelines)
- Identity & Consent Management
- CAMARA-API-access-and-user-consent.md
- CAMARA-AuthN-AuthZ-Concept.md
- Note: documents will be incorporated into Commonalities release at some point of time, until then they be referenced by Commonalities
- Release Management
- Overview of released APIs and their version and status
- Release management process
- For each (API) sub projects:
- API Definition(s)
- Following the Commonalities guidelines
- Successful linting check (with latest rules provided by Commonalities
- Inline documentation, usable together with swagger editor and redoc
- Test definitions
- .feature files according to guideline from Commonality (comes with v0.2.0)
- Supplementary documentation if needed to use or implement the API definition(s)
- User documentation should be including the API Definition
- API Definition(s)
- Commonalities
- Dependencies:
- Release Management <= Commonalities, API Sub Projects
- Needs information (e.g. scope definitions) about the planned and done releases from the sub projects
- This information has to be provided in a way that can be automated collected
- API sub project(s) <= Commonalities
- all API Sub Projects need to know the release of the Commonalities documents and artefacts which they have follow for their release
- Commonalities <= Identity & Consent management
- Commonalities (a release of Commonalities is referring to documents within a release of I&CM)
- Release Management <= Commonalities, API Sub Projects
- Potential milestones:
- Kick-off
- and Scope of I&CM and Commonalities
- 4 weeks
- Release candidates of Commonalities
- Scope defined per sub projects (could be part of one the previous lines)
- 4 weeks
- Release of Commonalities
- 4-6
- (First) Release Candidates of sub projects
- 4-6 weeks
- Sub project releases
- 2 weeks
- Common Release Date ("packaging done for the community release")
- Release Retro
- Kick-off
- Release cadence:
- 2 releases per year as a target
- Initial schedule:
...