Versions Compared

Key

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

DRAFT PROPOSAL FOR COMMENTS

The following items are expected to be completed for the project to Pass  Release Sign-Off Milestone.

Release Sign-Off 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 committed Product Backlog Stories been coded and marked as "Done" in Jira?Link to JiraYes
  • Closed/Done:
    Jira Legacy
    serverSystem Jira
    jqlQueryproject = oom AND type = Story AND fixversion = "Amsterdam Release" and status in (Closed, Delivered, Done)
    counttrue
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
  • Open:
    Jira Legacy
    serverSystem Jira
    jqlQueryproject = oom AND type = Story AND issuetype != Bug AND fixversion = "Amsterdam Release" and status in (Open, "In Progress", "To Do")
    counttrue
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

Are all tasks associated with committed Product Backlog Stories been marked as "Done" in Jira?Link to JiraYes
  • Closed/Done:
    Jira Legacy
    serverSystem Jira
    jqlQueryproject = oom AND type = Story AND fixversion = "Amsterdam Release" and status in (Closed, Delivered, Done)
    counttrue
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
  • Open:
    Jira Legacy
    serverSystem Jira
    jqlQueryproject = oom AND type = Story AND fixversion = "Amsterdam Release" and status in (Open, "In Progress", "To Do") and issuetype != Bug
    counttrue
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

Provide the project feature list.Link to evidenceYes

Jira Legacy
serverSystem Jira
columnskey,summary,type,description
maximumIssues20
jqlQueryproject = oom AND type = Epic AND fixversion = "Amsterdam Release" order by priority
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176


Summarize any functionalities that were planned at Release planning and not delivered at Release Sign-Off


  • Full Configuration Management through OOM not completed. Will spillover through Beijing

Release ManagementHave all issues pertaining to FOSS been addressed?Yes

Have all findings from previous milestones been addressed?Provide link to JIRA findingsYes

DevelopmentAre all the Jenkins jobs successfully passed (verify + merge jobs)?N/a

Are all binaries available in Nexus?Provide link to evidenceN/ANot applicable for R1.

Are all Docker images available In Nexus?Provide link to evidenceN/ANot applicable for R1.

Integration and Testing

Have all CSIT Use Cases (created by each project team) passed?Provide link to evidenceN/ANot applicable for R1.Goal is to incease our confidence the latest commit did not break the major functionality. Jenkins CSIT Jobs
Has the project code successfully passed the Daily Build process?Provide link to evidenceN/ANot applicable for R1.
Goal is to ensure the latest project commit has not broken the Integration Daily Build 

Has the project done the integration testing with related dependent projects?

N/ANot applicable for R1.
Documentation

Has your team contributed and completed work in the following documentations in ReadTheDocs:

  1. Release Notes
  2. Project Documentation
Yes

Provide Link to ReadTheDocs Release NotesProvide Link to ReadTheDocs Project Documentation

http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/