The following items are expected to be completed for the project to Pass the M4 Code Freeze Milestone.
- Use the "Copy" option (available under the ..., top right of this page) to duplicate this template into your project wiki.
- Fill out the Yes/No column
- Provide link to evidence (when necessary)
|Practice Area||Checkpoint||Yes/No||Evidences||How to?|
|Product Management||Have all JIRA Stories supporting the release use case been implemented?||yes||For each JIRA story that are implemented in Amsterdam Release, you have to setup in JIRA the JIRA fixVersion="Amsterdam Release"|
|List the Stories that will not be implemented in this current Release.|
Model alignment and VNF Requirements alignment stories postponed to Casablanca. Models were not published prior to M4 and the impact of VNF requirements was unclear. VNFSDK-167 (implement AAF authentication) deferred because implementing now would break SDC integration.
For each JIRA story that will not be implemented in Amsterdam Release, you have to setup in JIRA the JIRA fixVersion="Beijing Release"
|Are committed Sprint Backlog Stories been coded and marked as "Done" in Jira?|
|Are all tasks associated with committed Sprint Backlog Stories been marked as "Done" in Jira?||mostly|
Ice tools have been imported, but not yet integrated with marketplace. VNFSDK-215 is has been deferred to Casablanca.
|Release Management||Have all issues pertaining to FOSS been addressed?||yes|
|Have all findings from previous milestones been addressed?||yes||For M2 and M3 Milestones, ensure all findings have been closed.|
|Development||Are all Defects of priority Highest and High in status "Done" in Jira?||yes|
|Is there any binaries (jar, war, tar, gz, gzip, zip files) in Gerrit project repository?||no||Refer to CI Development Best Practices|
|Is there any pending commit request older than 36 hours in Gerrit?||no||https://gerrit.onap.org/r/#/q/status:open+vnfsdk|
|Are all the Jenkins jobs successfully passed (verify + merge jobs)?||yes|
(currently a minor error with vet-agent, should be cleared by Thurs)
|Are all snapshot binaries available in Nexus?||yes||https://nexus.onap.org/content/repositories/snapshots/org/onap/vnfsdk/|
|Do you have a clear plan to implement the Independent Versioning and Release Process by RC0?||yes||continuing from Amsterdam release||Contact the upstream teams to make sure they will release their artifacts (in Nexus Release repo) so you can build by depending on these released artifacts by RC0.|
|Integration and Testing||Have 100% of Continuous System Integration Testing (CSIT) Use Cases been implemented successfully in Jenkins?||yes||https://jenkins.onap.org/view/CSIT/|
|Is there a Docker images available for your project deliverable?||yes|
|Has the project code successfully passed the Daily Build process?||yes||https://jenkins.onap.org/view/vnfsdk/||Goal is to ensure the latest project commit has not broken the Integration Daily Build|
|Doc||Has the team created a docs folder and Development and Release Notes documentation templates in Readthedocs?||yes||http://onap.readthedocs.io/en/amsterdam/submodules/vnfsdk/model.git/docs/index.html|
ReadTheDcos shall be considered as a starting point for someone new within ONAP.
The ReadTheDocs is the ONAP Documentation facade visible to users.
Link to Templates
|Is the API documentation section populated?||yes||http://onap.readthedocs.io/en/amsterdam/submodules/vnfsdk/model.git/docs/index.html||Ensure there is at least a direct link toward the API documentation which may be already existing in the wiki.|