WORK IN PROGRESSREADY FOR REVIEW
API Sub-projects are used to develop and support releasing APIs.
- One API Sub-project ideally contains one API or a small set of closely related APIs.
- A release includes all the APIs of the API Sub-project.
- Hence a public-release can only be created when all APIs in the API Sub-project have at least an initial public-release API version.
...
API Sub-projects may have one of the follow maturity status:
- Sandbox
- Incubated
By default an API Sub-project has the Sandbox maturity status.
An API Sub-project needs to minimally respect the following requirements to obtain a the Incubated maturity status:
- It participates participated in at least 1 meta-release cycle
- It is managed through regular scheduled meetings with MoMs meeting minutes being provided.
- It has adopted LF - tools (Zoom, wiki, ...) and uses them according to the CAMARA guidelines.
The maturity status is determined by the TSC base based on these and the below requirements.
...
An Incubated API Sub-project can manage and evolve in parallel APIs with stable versions (1.x.y) and initial versions (0.x.y).
An Incubated API Sub-projects have has to follow the meta-release cycle for all included APIs.
...