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

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 "Done" in Jira?
Link to Jira

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


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. 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, has the team populated and validated all the sections in the Documentation template? These information must be useful for installation, configuration, and usage.

For RC1, has the team addressed to issue (recorded in JIRA) provided by the Documentation team?

For RC2, have all remaining issues been addressed?

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



Documentation Team is using ReadTheDocs for documenting user facing documentation.
  • No labels