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 7 Next »

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 AreaCheckpointYes/NoEvidencesHow to?
Product ManagementAre all tasks associated with the release been marked as "Done" in Jira?No

The following Casablanca Open Stories for OOM remain and will be closed once final patches are reviewed and have been merged.




Have all findings from previous milestones been addressed?YesProvide link to JIRA findings
DevelopmentHave all Defects of priority Highest and High been in status "Done" in Jira?Yes

All OOM Highest Priority Defects have been resolved.


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

There are no Highest or High Priority issues older than 36 hours.

https://gerrit.onap.org/r/#/q/project:oom+and+status:open+and+age:36h


There are, however, a larger than desirable backlog of patches due to the OOM team's heavy involvement assisting project teams with competing their development and integration work.


Are all the Jenkins jobs successfully passed (verify + merge jobs)?Yeshttps://jenkins.onap.org/view/oom/job/oom-master-merge-helm/

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

There are Helm Chart artifacts in the Staging repo in Nexus:

https://nexus.onap.org/content/sites/oom-helm-staging/

Refer to Independent Versioning and Release Process for procedure
Integration and TestingHave all CSIT Use Cases (created by each project team) passed?N/AProvide link to evidence. As things are moving fast, we want to ensure CSIT are still "green".
At RC0, has the Pair Wise testing table been filled out?N/A

At RC0, have all OOM Release Healtcheck related to your project passed?N/A
Goal is to ensure the latest project commit has not broken the Integration Daily Build 
At RC0, is there a Docker image in Nexus Docker-Release repo available for each repository?N/A

Has the project code successfully passed the Daily Build process?N/A
Goal is to ensure the latest project commit has not broken the Integration Daily Build
Has the OOM deployment passed?N/AEnsure in Jenkins External Labs all Health Check pass.

Has the Heat deployment passed?

(not a gating item for Casablanca)

N/AEnsure in Jenkins External Labs all Health Check pass.
Documentation

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


N/A

The OOM Documentation is here: http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_project_description.html

There are four documents including a User Guide.

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?




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?


  • No labels