CPS-TBDMT Deprecation

1

Final call to the ONAP Community raised by the PTL or by the TSC or TSC-Delegate. (Negative Result for volunteer for succession results in following steps).

Done

@Toine Siebelink initiated the deprecation

2

Review what is used by the Community and the dependencies to other components and maintain the repositories that are necessary for the ONAP Components

Done

ONAPARC-808: CPS-TBDMT deprecation for OsloClosed

3

Verify what (if any) impact the change has on OOM/Integration (CIST)/DOC projects and ensure that is communicated

Done

ONAPARC-808: CPS-TBDMT deprecation for OsloClosed

4

If the repo(s) are still required, then Identify an alternative path (if any)

Done

TSC 2024-10-17

5

Identify potential remaining committers to maintain the remaining repositories.

Done

6

Make functionality retirement decision

Done

7

Update INFO.yaml with TBD (define fields, etc.)

Done

8

In gerrit set the appropriate repositories that are no longer in use  to 'Read Only' access

Done

9

Update the Architecture diagrams and references (Confluence)

Done

10

Update the Architecture diagrams and references (readthedocs)

@Thomas Kulik

To do

11

Indicate in the release note that the project is in Unmaintained state i.e. add a hint in the header.

Done

https://gerrit.onap.org/r/c/cps/cps-tbdmt/+/139253?usp=search

12

Remove Jenkins jobs (I think Code scanning and report generation needs to continue until closed and archived)

Done

https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-27372

13

Move the project to Unmaintained State Projects including Clean-up of other wiki pages, RDT, JIRA, Jenkins Job, CLM, SonarCloud, mailing lists, calendars, etc. 

Done

https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-27372

14

The project information for this component will no longer be branched (i.e. master) and will be linked to final maintained release_XXX. (LF-IT to adjudicate changes to CI tools)

Done

@Andreas Geißler , confirmed nothing needs to be done for this deprecation

15

Note:  the following applies only if the project or component is reintroduced to a release after being archived.

Any critical, severe or high vulnerability found in the code written by the project team MUST be fixed within 60 days or prior to the inclusion of the project in a new release, whichever occurs first. (This can not be done due to lack of resources.

1. If committers are still around, provide a fix 

2. If the fix is not possible, open CVE, and Update release notes

N/A