Versions Compared

Old Version 4

changes.mady.by.user Randa Maher

Saved on

compared with

New Version Current

changes.mady.by.user Randa Maher

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

RC Release Candidate Milestone overview is available in wiki.


Info
titleUsage
  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?Yes, with the exception of a couple of documentation items, which should be completed by next week.Link to Beijing Jira

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?

In-progress;

Provide link to JIRA issue (type bug) of priority

Yes



Highest and High

. 

Jiras


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)?In-ProgressYes

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

APPC-905



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.

In-progress; anticipate doing release on 5/17Yes
Refer to Independent Versioning and Release Process for procedure
Integration and TestingHave all CSIT Use Cases (created by each project team) passed?YesProvide link to evidence. As things are moving fast, we want to ensure CSIT are still "green".
Is there a Docker images available for each repository?In-progressYesProvide link to evidence
Has the project code successfully passed the Daily Build process?In-progressYes

APPC-906 - request to LF for more space: https://gerrit.onap.org/r/#/c/47915/

Also addressing APPC-905

Goal is to ensure the latest project commit has not broken the Integration Daily Build 
Has the OOM deployment passed?YesEnsure in Jenkins External Labs all Health Check pass.
Has the Heat deployment passed?YesEnsure 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

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

In-progressYes

For RC2, has the Documentation Team provided the final approval for your project documentation?In-progressN/A - Documentation team does not provide approval for our documentation; I'm not aware of new documentation requirements in Beijing.