Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

The following items are expected to be completed for the project to Pass the M4 Code Freeze Milestone.

M4 Release Code Freeze Milestone overview is available in wiki.

Practice AreaCheckpointYes/NoEvidencesHow to?
Product ManagementHave all JIRA Stories supporting the release use case been implemented?Yes

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)

Getting issues...

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

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)

Getting issues...

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?YesProvide Link to Project backlog
Are all tasks associated with committed Sprint Backlog Stories been marked as "Done" in Jira?In Progress

Release ManagementHave all issues pertaining to FOSS been addressed?


Have all findings from previous milestones been addressed?
List previous milestone issues that have not been addressed.For M2 and M3 Milestones, ensure all findings have been closed.
DevelopmentAre all Defects of priority Highest and High in status "Done" in Jira?In ProgressProvide 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

https://jenkins.onap.org/view/vid/job/vid-master-merge-java/

https://jenkins.onap.org/view/vid/job/vid-asdcclient-master-merge-java/


Are all snapshot binaries available in Nexus?Yeshttps://nexus3.onap.org/#browse/search=keyword%3Dvid
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 TestingHave 100% of Continuous System Integration Testing (CSIT) Use Cases been implemented successfully in Jenkins?Yeshttps://jenkins.onap.org/view/vid/job/vid-master-csit-healthCheck/
Is there a Docker images available for your project deliverable?Yeshttps://nexus3.onap.org/#browse/search=keyword%3Dvid
Has the project code successfully passed the Daily Build process?Yeshttps://jenkins.onap.org/view/vid/job/vid-master-release-version-java-daily/233/Goal is to ensure the latest project commit has not broken the Integration Daily Build 
DocHas the team created a docs folder and Development and Release Notes documentation templates in Readthedocs?
Add a link to your project documentation in ReadTheDocs.

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

How to setup the template for my project?

Is the API documentation section populated?YesVID R1 Amsterdam API DocumentationEnsure there is at least a direct link toward the API documentation which may be already existing in the wiki.
  • No labels