...
Component Dependecy Matrix (in progress); Flow matrix
Maintenance:
- Project(s) or sub-project(s) is no more part of any official release, but some parts might still be consumed indirectly by other project teams or some functionalities are still needed but no alternative has been implemented yet.
- These Project(s) or sub-project(s) are no more subject to non-functional compliances. The level of support will be dependent on the ONAP Community willingness to contribute, fast response time is not guaranteed.
- The project will be still part of OOM deployment and High Priority bugs might be fixed to unblock the current and/or maintained releases.
Transition from Maintenance to Incubation/Mature: A maintenance project can be moved to “Incubation” or “Mature if there is a new interest from the ONAP Community including PTL responsibility and committers engagement, reviewed and approved by the ONAP TSC. The project will be still part of OOM deployment and High Priority bugs might be fixed to unblock the current and/or maintained releases
Transition from Maintenance to Archived: A maintenance project can be moved to “Archived" if the project is no more critical for the ONAP Platform (Deployment, Onboarding, Instanstiation, Run-Time) or has any dependecy to any ONAP component.
...
#10 Move Logging to Project State: Archived following the Termination Review process (incl. Clean-up of other wiki pages, RDT, JIRA, mailing lists, calendars, etc.)
#11 Indicate in the release note that the project is in maintenance i.e. add a hint in the header.
#12 The project information for this component will no more be branched (i.e. master) and will be linked to the latest maintained release.
5. Additional link(s)/reference(s)
6. Action Items
- (SECCOM) Finalize the component dependency Matrix - Flow matrix
- (Architecture Subcommittee) Define ONAP MVP components
- (Chaker/Jason) Add Project State Maintenance to the Project Lifecycle deck