Skip to end of metadata
Go to start of metadata

DRAFT PROPOSAL FOR COMMENTS

The following items are expected to be completed for the project to Pass the Release Candidate Milestone.

This template must be filled out for every Release Candidate Milestone (RC0, 1, 2, x)

RC Release Candidate Milestone overview is available in wiki.



Practice AreaCheckpointYes/NoEvidencesHow to?
Product ManagementAre all tasks associated with the release been marked as "Done" in Jira?YesLink to Jirano new functionality in Beijing release - see project plan

Have all findings from previous milestones been addressed?YesProvide link to JIRA findingsM4 completed
DevelopmentHave all Defects of priority Highest and High been in status "Done" in Jira?YesProvide link to JIRA issue (type bug) of priority Highest and High. 
Are all JIRA issues used as a reference in a commit in status "Done" in Jira?YesLink to JIraVery often, some JIRA issue remains in status "Todo" in JIRA while the commit they are referenced to is successful.
Is there any pending commit related to Highest and High priority issues older than 36 hours in Gerrit? In case there are messages going back and forth between authors and reviewers, it is acceptable to be above 36 hours.NoLink to gerritt
Are all the Jenkins jobs successfully passed (verify + merge jobs)?NAProvide link to verify  "Merge job" as evidence in Jenkins project tabdependent on OOM build

Has the team delivered all their release artifacts in Nexus Release or Nexus Staging repo?

There should be at least ONE version of each artifacts available in Nexus Release or Nexus Staging repo.

Yes

Nexus link

Nexus / Docker link

Refer to Independent Versioning and Release Process for procedure
Integration and TestingHave all CSIT Use Cases (created by each project team) passed?NAProvide link to evidence. As things are moving fast, we want to ensure CSIT are still "green".dependent on OOM build
Is there a Docker images available for each repository?yesProvide link to evidence
Has the project code successfully passed the Daily Build process?yesLinkGoal is to ensure the latest project commit has not broken the Integration Daily Build 
Has the OOM deployment passed?NoEnsure in Jenkins External Labs all Health Check pass.Pending OOM creation of Helm charts
Has the Heat deployment passed?NAEnsure in Jenkins External Labs all Health Check pass.Native Docker implementation - no HEAT build option
Documentation

For RC0, for project delivering binaries, has the team populated and validated all the sections of either the Platform Component or SDK template?


NAVVP is a stand alone tool, not a platform component or SDK template.

Most teams have already created the high level file structures in readthedocs, and populated some actual documentation. However, the remaining sections of the appropriate teamplate must be completed.

Platform: A&AI, APP-C, CLAMP, CLI, DCAE, DMaaP, Holmes, MSB, OOM, Policy, Portal, SDN-C SDC, SO, UseCase UI, VFC, VID

SDKs: AAF, CCSDK, External API Framework, Multi VIM/Cloud, VNFSDK

For RC1, has the team addressed any issue (recorded in JIRA) provided by the Documentation team?

Yes
No Doc JIRA tickets against VVP

For RC2, for project delivering binaries, has the team populated and validated all the sections of the Release Notestemplate?




For RC2, has the Documentation Team provided the final approval for your project documentation?