According to ONAP Guilin Release requirement input Guilin Release Requirements
Gather requirement: March
Refine requirement:
Reporting on the Guilin release to the TSC will begin nnn, so the deadline for the input of high level reuiqrement will be nnn.
Prioritize & Finalize:
before M1: nnn , the requirement will be finalized.
There are other 5 categories of high level requirement,
- 1) Will be implemented in R6 by code commitment to different impacted projects/components.
- 2) Will document only for the Frankfurt release.
- 3) Documentation after implemented in prior release
- 4) Lower Priority
- 5) Experimental
The first category is that those requirement will be documented only in Guilin release
the second category will document the current implementation in those projects.
Other two categories like lower priority and experimental will not be included in the release 3, the contributor will work with best effort to influence future release.
Owners of each requirement needs to coordinate the modeling spec commitment and code commitment with PTLs of impacted project.
Below High Level Requirements have been agreed by modeling subcommitee with code commitment promise to Frankfurt release, modeling subcommittee request related to projects to approve those related submission.
Category 1) will be implemented in the Guilin release
Modeling Domain | Modeling Requirement | Modeling Requirement Description | Impacted Projects | Use Case Relevance | Modeling Spec Commitment | Code Commitment | Provider Priority | Mapping to M1 requirement | Owner | Use Case Owner |
---|---|---|---|---|---|---|---|---|---|---|
Category 2) Will document only for the Guilin release
Modeling Domain | Modeling Requirement | Modeling Requirement Description | Impacted Projects | Use Case Relevance | Modeling Spec Commitment | Code Commitment | Provider Priority | Mapping to M1 requirement | Owner | Use Case Contact |
---|---|---|---|---|---|---|---|---|---|---|
Category 3) Documentation Only after implemented in prior release
Modeling Domain | Modeling Requirement | Modeling Requirement Description | Impacted Projects | Use Case Relevance | Modeling Spec Commitment | Code Commitment | Provider Priority | Mapping to M1 requirement | Owner |
---|---|---|---|---|---|---|---|---|---|
Below tables are not downgrade, but Guilin won't make it
Category 4) Lower Priority:
Modeling Domain | Modeling Requirement | Modeling Requirement Description | Impacted Projects | Use Case Relevance | Modeling Spec Commitment | Code Commitment | Provider Priority | Owner |
---|---|---|---|---|---|---|---|---|
Category 5) Experimental:
Modeling Domain | Modeling Requirement | Modeling Requirement Description | Impacted Projects | Use Case Relevance | Modeling Spec Commitment | Code Commitment | Provider Priority | Owner |
---|---|---|---|---|---|---|---|---|
Per discussion in Paris, requirements can be based on:
- Release / project specific needs
- Recognized 'future' needs
- Documenting existing models
Some concepts may be complex enough, if we wait for the release / project requirement, we will be too late to properly develop the concept.