Versions Compared

Key

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

...

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?
Link to Jira
Release Management(For RC0 only) As the project team identified the reduced set of Committers who will proceed with Code Merge after RC0?
Provide the name of committers. Recommendation is 3 committers max per project (1 per geographic area)?


Have all findings from previous milestones been addressed?
Provide link to JIRA findings
DevelopmentHave all Defects of priority Highest and High been in status "Done" in Jira?
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?

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
request 
related to Highest and High priority issues older than
24
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.


Are all the Jenkins jobs successfully passed (verify + merge jobs)?
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.



Refer to Independent Versioning and Release Process for procedure
Integration and TestingHave all CSIT Use Cases (created by each project team) passed?
Provide link to evidence
Have all end-to-end CSIT (created by Integration Team) been identified (for RC0) and passed (for RC1)?Provide 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?
Provide link to evidence
Has the project code successfully passed the Daily Build process?

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

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




Most teams have already created the high level file structures in

the Documentation template? These information must be useful for installation, configuration, and usage.

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

to

any issue (recorded in JIRA) provided by the Documentation team?




For RC2,

have all remaining issues been addressed

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?
Documentation Team is using ReadTheDocs for documenting user facing documentation.