Roadmap ¶
Table of Contents ¶
Overview ¶
- The activities of the CNTT community are articulated around Projects , Milestones and Releases .
- CNTT is embracing simultaneous delivery model, meaning that all contributing projects have to follow the cadence and intermediate milestones.
- Each CNTT release is the only delivery vehicle and is common for all projects.
- The CNTT current release plan is available here .
Figure 1: Milestones
Definitions
- Long term endeavour setup to deliver features across multiple releases as shown here
- Led by leads/co-leads, contributors and committers with expertise in the relevant areas
- Scripted and documented in repositories
- Short term endeavour setup to deliver a specific features/functionalities as shown here .
- An agreed common framework (template, criteria, best practice) for all projects
- An unique release planning calendar with pre-defined milestones for each project
- A vehicle to coordinate multiple projects and multiple type of projects (reference model and architecture, documentation, integration, packaging, deployment)
A Bundle is: A set of related specifications that are built to complement each other, specifically (RM -> RA -> RC -> RI).
-
Each document within a release has a number attached to it that consists of
Bundle.Version
:
- Bundle : specifies the bundle number of which the the document belongs to.
- Version : specifies the sequential version of each document (improvement or enhancements).
- Any Change in RM that will impact RAs and consequently RC and RI will triggers a new Bundle number.
Roadmap ¶
Detailed Milestones ¶
| Review | Milestone | Description | Activities | Comments | |——–|———–|————–|————|———| | Kick-Off | M0 | The goal of the release Kick-Off is to open the innovation platform for the intent to participate in the CNTT release. Release Kick-Off review takes place for each releases. | Name the Release and create appropriate labels in GitHub. || | Planning & Scoping | | The goal of the Release Planning & Scoping is to capture the initial set of features and functionality that should be part of the release along with prioritisation. |
- Identity a list of features and functionality including from the backlog will be developed and documented as part of the current release. N.B. Feature/functionality, errors etc. are logged in GitHub as Issues.
- Identify what is in or out of scope for the release.
- Escalate any issues to the TSC.
- After the review cut-off date any major features & functionalities changes will be added to the backlog unless it is approved by the TSC to be added into the current scope of release.
- Bug fixes or any minor changes identified during the development will be allowed.
- For any other content changes to be approved by TSC.