SDNC : Beijing RC0 : Milestone Checklist Template

Owned by Dan Timoney
Last updated: Apr 17, 2018 by Christopher McCray
2 min read

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.



Usage

  1. Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki.

  2. Fill out the Yes/No column

  3. Provide link to evidence (when necessary)

Practice Area

Checkpoint

Yes/No

Evidences

How to?

Practice Area

Checkpoint

Yes/No

Evidences

How to?

Product Management

Are all tasks associated with the release been marked as "Done" in Jira?

Yes

Link to Jira





Have all findings from previous milestones been addressed?

Yes

Provide link to JIRA findings



Development

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

Yes

Provide 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?

Yes



Very 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.

No





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

Yes

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



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



Refer to Independent Versioning and Release Process for procedure

Integration and Testing

Have all CSIT Use Cases (created by each project team) passed?

No

There is a pending change (https://gerrit.onap.org/r/#/c/42731/) to address this issue.  Build is failing due to incorrect password, which is changed in this fix.



Is there a Docker images available for each repository?

Yes

Provide link to evidence



Has the project code successfully passed the Daily Build process?

Yes



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

Has the OOM deployment passed?

No

Failing due to incorrect password being used.



Has the Heat deployment passed?

No

Failing due to incorrect password being used.



Documentation

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



Yes



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?

N/A





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

N/A





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

N/A