[vnfrqts] M4 Deliverables for Code Freeze Milestone Checklist Template

Product Management

All all JIRA Stories supporting the release use case been implemented?

Yes

EPIC - prototype RFP text

By using the macro JIRA Issue/Filter, provide a link to JIRA in listing the stories that are implemented in Amsterdam Release. (Example 86 issues for AAI project, edit for your project)

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.

YES

All EPICS other than prototype RFP text

By using the macro JIRA Issue/Filter, provide a link to JIRA in listing the stories that are NOT implemented in Amsterdam Release. (Example 3 issues for AAI project, edit for your project)

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?

Yes

Provide Link to Project backlog

Are all tasks associated with committed Sprint Backlog Stories been marked as "Done" in Jira?

Yes

Link to Project backlog

Release Management

Have all issues pertaining to FOSS been addressed?

Yes

This project provides only documentation

Have all findings from previous milestones been addressed?

Yes

Provide link to JIRA findings

M1,M2 M3 passed

Development

Are all Defects of priority Highest and High in status "Done" in Jira?

Yes

Provide link to JIRA issue (type bug) of priority Highest and High. 

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

Are all the Jenkins jobs successfully passed (verify + merge jobs)?

Yes

Provide link to "Merge job" as evidence in Jenkins project tab

Are all snapshot binaries available in Nexus?

Yes

Provide link to evidence

documentation delivered to onap.readthedocs.io rather than nexus

Do you have a clear plan to implement the Independent Versioning and Release Process by RC0?

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?

N/A

All jobs pertaining to your project MUST pass

documentation toolchain driven by documentation project

Is there a Docker images available for each repositories?

N/A

Has the project code successfully passed the Daily Build process?

N/A

documentation not code

Goal is to ensure the latest project commit has not broken the Integration Daily Build 

Doc

Has the team created a documentation Template in ReadTheDocs?

Yes

Add a link toward the your project documention in ReadTheDocs.

Documentation Team is using ReadTheDocs for documenting user facing documentation.

ReadTheDcos shall be considered as a starting pint for someone new withn ONAP.

The ReadTheDcos is the ONAP Documentation facade visible to users.

Link to Template

How to setup the template for my project?

Is the API documentation section poplulated?

N/A

documentation not code so no VNFRQTS APIs to document

Ensure there is at least a direct link toward the API documentation which may be already existing in the wiki.