...
- Project can reach "Archived" state for multiple reasons. Either project has successfully been completed and its artifacts provide business values, or project has been cancelled for unforeseen reasons (no value anymore, technical, etc.).
- Project in any state can be "Archived" through a Termination Review.
3. Transition Steps
Transition from “Incubation/Mature/Core” to "Unmaintained"
A "Incubation/Mature or Core" project can be moved to “Unmaintained” if 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. The following steps will be performed:
#1 Final call to the ONAP Community raised by the PTL or by the TSC.
#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
#3 Identify potential remaining committers to maintain the remaining repositories
#4 Verify what (if any) impact the change has on OOM/Integration (CIST)/DOC projects and ensure that is communicated
#5 Update INFO.yaml
#6 In gerrit set the appropriate repositories that are no longer in use to 'Read Only' access
#7 Update the Architecture diagrams and references
#8 Remove Jenkins jobs
#9 Inform Steven Winslow (LFN IP Legal) and disable all the scans (Sonar, FOSSology, NexusIQ) on the unmaintained repos
#10 Identify an alternative path (if any)
#11 Move the project to Unmaintained State Projects including Clean-up of other wiki pages, RDT, JIRA, mailing lists, calendars, etc.
#12 Indicate in the release note that the project is in Unmaintained state i.e. add a hint in the header.
#13 The project information for this component will no more be branched (i.e. master) and will be linked to the latest maintained release.
#14 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.
Muddasar's Proposed format for above process. Some actions have been rearranged. An unmaintained project must provide User Docs, SW and release notes. The unmaintained project must also go thru quality assurance process to discover new vulnerabilities that can help improve release notes or a decision to remove the project from release (archived)
...
Any ONAP projects or its sub capabilities when no longer maintained should be subjected to this process to either create a maintain plan with in ONAP ecosystem or retire SW capability without creating adverse impact on ONAP.
Note: Anywhere in the steps below that "PTL" is in the "Responsible" column, it is assumed that the TSC will take that responsibility if the PTL is not available.
Tableenhancer |
---|
numberOfFixedRows | 1 |
---|
numberOfFixedColumns | 1 |
---|
|
| Action | Responsible | Accountable | Consulted | Informed |
---|
|
...
| Artifact | Tool/process |
---|
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). |
---|
|
...
PTL | TSC | PTLs | ArcSubComm SECCOM
| JIRA EPIC(new) Ticket ( highest priority/severity) | ONAP TSC JIRA Ticket (TSC on update CC) | 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 | ArcSubComm | TSC | PTLs, SECCOM | PTLs | JIRA EPIC-Tasks per project-New (Projects Dependency List) | ONAP JIRA, Nexus, PTL Assigned task updates, Weekly status on TSC Meeting |
---|
3 | Verify what (if any) impact the change has on OOM/Integration (CIST)/DOC projects and ensure that is communicated | ArcSubComm | TSC | PTLs, SECCOM, DOC | PTLs | JIRA Task update, impact assessment report | ONAP JIRA, Weekly status on TSC Meeting |
---|
|
...
4 | If the repo(s) are still required, then Identify an alternative path (if any) | ArcSubComm | TSC | PTLs | ArcSubComm, SECCOM | JIRA Task update, | Weekly status on TSC Meeting |
---|
|
...
5 | Identify potential remaining committers to maintain the remaining repositories. | TSC | TSC | PTLs | ArcSubComm, SECCOM | Info.yaml to look up, JIRA | TSC delgation, ONAP JIRA, Gerrit Repo. |
---|
|
...
...
Make functionality retirement decision | TSC | TSC | ArchSubComm, SECCOM | Arc, Sec, PTLs | JIRA update LFN IT Jira issue for updating INFO.yaml | ONAP JIRA |
|
...
...
.yaml with TBD (define fields, etc.) | PTL, Contributor (if available), LF IT | TSC | None | ArcSubComm, SECCOM, PTLs |
|
...
...
Committer, Super Committer, |
|
...
...
...
8 | In gerrit set the appropriate repositories that are no longer in use to 'Read Only' access |
---|
|
...
PTL (make request if available), LF-IT | PTL TSC (if no PTL) | None | ArcSubComm, SECCOM, PTL (if available) TSC | ONAP JIRA, LF IT JIRA | ONAP JIRA, LF IT JIRA, gerrit, github | 9 | Update the Architecture diagrams and references (Confluence) | ArchSubComm | TSC | None | Doc, ArcSubComm, SECCOM, PTL (if available) | ONAP JIRA, wiki | ONAP JIRA, confluence |
---|
10 | Update the Architecture diagrams and references (readthedocs) | Doc | TSC | ArcSubComm | None | readthedocs | readthedocs |
---|
| Indicate in the release note that the project is in Unmaintained state i.e. add a hint in the header. | PTL | TSC | None | None | User Docs, Release Notes | ONAP JIRA Updates, WIKI, ONAP.read the docs |
---|
11 |
---|
|
...
Tableenhancer |
---|
|
Sequence | Action | R | A | C | I | Artifact | Tool/process | 1 | Final call to the ONAP Community raised by the PTL or by the TSC. (Negative Result for volunteer for succession) | TSC | TSC | PTLs | ArcSubComm SECCOM | JIRA EPIC(new) Ticket ( highest priority/severity) | JIRA Ticket | 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 | ArcSubComm | TSC | PTLs, SECCOM | PTLs | JIRA EPIC-Tasks per project-New (Projects Dependency List) | JIRA, Nexus, PTL Assigned task updates, Weekly status on TSC Meeting | Verify what (if any) impact the change has on OOM/Integration (CIST)/DOC projects and ensure that is communicated | ArcSubComm | TSC | PTLs, SECCOM, DOC | PTLs | JIRA Task update, impact assessment report | JIRA, Weekly status on TSC Meeting | 3 | Identify an alternative path (if any) | ArcSubComm | TSC | PTLs | ArcSubComm, SECCOM | JIRA Task update, | Weekly status on TSC Meeting | 4 | Identify potential remaining committers to maintain the remaining repositories | TSC | TSC | PTLs | ArcSubComm, SECCOM | Info.yaml to look up, JIRA | TSC delgation, JIRA, Gerrit Repo. | 5 | Decision to retire functionality made | TSC | TSC | Arc, Sec, PTLs | JIRA update | JIRA | 6 | Update INFO.yaml | LFN IT | JIRA task | PTL, Commiter, Super Committer, Pam, LF-IT | 7 | In gerrit set the appropriate repositories that are no longer in use to 'Read Only' access | LF-IT? | 8 | Update the Architecture diagrams and references (Need role assignment) | 9 | Remove Jenkins jobs (I think Code scanning and report generation needs to continue until closed and archived) | PTL (make request if available), LF-IT |
---|
?10Inform Steven Winslow ( we should create alias as functions may be served by new staff) (LFN IP Legal) and disable all the scans (Sonar, FOSSology, NexusIQ) on the unmaintained repos (I think Code scanning and report generation needs to continue until closed and archived) | Pgm | TSC | PTLs | ArcSubComm, SECCOM | PTL (if available) | JJBs | Jenkins | 12 |
---|
11 Unmaintained State Projects including Unmaintained State Projects including Clean-up of other wiki pages, RDT, JIRA, mailing lists, calendars, etc. | (Need role assignment, tis may be multiple actions executed by multiple entities) | Project Management & its delegate | TSC | None | None | JIRA Tickets Updates | JIRA ONAP, JIRA LF-IT | 14 |
---|
12 | Indicate in the release note that the project is in Unmaintained state i.e. add a hint in the header. | DOC | 13 | The project information for this component will no |
---|
more longer be branched (i.e. master) and will be | linked to the latest linked to final maintained release_XXX. ( | how would it impact LF-IT to adjudicate changes to CI tools | ?) | LF-IT, Integration, Release Mgt | 14 | TSC | ArchSubComm | SECCOM | email | ONPA JIRA, LF-IT JIRA Updates | 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. |
---|
Can this be mentioned in the Release notes? if yes, who owns the risk? TSC?, SECCOM?) 1) If committers are still around, provide a fix 2) If the fix is not possible, open CVE, and Update release notes
| TSC, SECCOM, Documentation | TSC | PTLs, Committers (volunteer PTLs) | ArchSubCom, Documentation | Conf Calls, email | CVE, Documentation, ONAP JIRA, LF-IT JIRA. |
|
Transition from "Unmaintained" to "Incubation/Mature": A Unmaintained project can be moved to “Incubation” or “Mature" if there is a new interest from the ONAP Community and meeting the requirement for the project state while performing a project review, including PTL responsibility and committers engagement. The following steps will be re-initiatied
...