...
The following items are expected to be completed for the project to Pass Release Sign-Off Milestone.
Release Sign-Off Milestone overview is available in wiki.
Info | ||
---|---|---|
| ||
|
...
Practice Area | Checkpoint | Yes/No | Evidences | How to? |
---|---|---|---|---|
Product Management | Are committed Product Backlog Stories been coded and marked as "Done" in Jira? | yes | SO Jira | |
Are all tasks associated with committed Product Backlog Stories been marked as "Done" in Jira? | yes | SO Jira | ||
Provide the project features list under the form of a bulleted list. | yes | so readthedocs | ||
Summarize any functionalities that were planned at Release planning and not delivered at Release Sign-Off | YesNA | All functionlaities deliverd as per the initial plan | PNF was ready from SO side, but dropped for the ONAP Beijing release | |
Release Management | Have all issues pertaining to FOSS been addressed? | NA | ||
Have all findings from previous milestones been addressed? | Yes | No Pending tasks from previous milestones | ||
Development | Are all the Jenkins jobs successfully passed (verify + merge jobs)? | yes | SO Jenkins | |
Are all binaries available in Nexus Release repository? | yes | SO nexus release | ||
Are all Docker images available In Nexus? | yes | SO 1.2.2 | ||
Are the Java and Docker manifest updated with the same version as in Nexus Release repository? | yes | |||
Integration and Testing | Have all CSIT Use Cases (created by each project team) passed? | yes | SO Jenkins | Goal is to incease our confidence the latest commit did not break the major functionality. Jenkins CSIT Jobs |
Has the project code successfully passed the Daily Build process? | yes | SO Jenkins | Goal is to ensure the latest project commit has not broken the Integration Daily Build | |
Has the project done the integration testing with related dependent projects? | Yes | SO integration status | ||
Documentation | Has your team contributed and completed work in the following documentations in ReadTheDocs:
| Yes |