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

Version 1 Current »

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 "Closed" in Jira?YesLink to Jira

Have all findings from previous milestones been addressed?YesProvide link to JIRA findingsNo Prior issues
DevelopmentHave all Defects of priority Highest and High been in status "Closed" 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 "Closed" 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.noLink
Are all the Jenkins jobs successfully passed (verify + merge jobs)?NAProvide link to "Merge job" as evidence in Jenkins project tabrely on documentation project

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

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

NAdocumentation projectRefer 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".documentation project
At RC0, has the Pair Wise testing table been filled out?NACasablanca Pair Wise Testing master pagedocumentation project
At RC0, have all OOM Release Healtcheck related to your project passed?NAdocumentation project
At RC0, is there a Docker image in Nexus Docker-Release repo available for each repository?NAProvide link to evidencedocumentation project
Has the project code successfully passed the Daily Build process?NAdocumentation projectGoal is to ensure the latest project commit has not broken the Integration Daily Build 
Has the OOM deployment passed?NAEnsure in Jenkins External Labs all Health Check pass.documentation project

Has the Heat deployment passed?

(not a gating item for Casablanca)

NAEnsure in Jenkins External Labs all Health Check pass.documentation project
Documentation

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


NAdocumentation project

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

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

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


  • No labels