Versions Compared

Key

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

...

Project NameEnter the name of the project
Target Release NameEnter the name of the release you are targeting to deliverGuilin
Project Lifecycle StateEither Incubation, Core, Mature. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information
Participating Company List the company participating in this release. At least 3-4 organizations, including an operator are recommended

See gerrit for the different Integration related repositoriries

  • integration/*
  • testsuite/*
  • demo/*

Declarative wiki text is just declarative.

Fortunately gerrit has all this information, dynamically updated and easily auditable.

Scope

What is this release trying to address?

Describe the problem being solved by this release

Requirements

...

Same scope as usual

  • ensure integration
  • perform CI
  • support Intel/Windriver lab usage
  • support use cases

See Integration EPICs for new topics

Requirements

N.A

Minimum Viable Product

Describe the MVP for this release.

Functionalities

List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.

...

N.A

Functionalities

A dedicated Dashboard has been created for Guilin: https://jira.onap.org/secure/RapidBoard.jspa?rapidView=221&selectedIssue=INT-1045

Epics

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject=INTEGRATION and issuetype in (epic)
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject=TEST and issuetype in (epic)
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

Stories


Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject=sanbox INTEGRATION and issuetype in (epicstory)
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

...


Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject=sanbox TEST and issuetype in (story)
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176


Longer term roadmap

Indicate at a high level the longer term roadmap. This is to put things into the big perspective.More tests, More automation, More CI chains

Release Deliverables

Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note, etc) of this release.

...

Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.

...

List the API this project is expecting from other projects.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.

Prior to the delivery date, it is a good practice to organize an API review with the API consumers.

...

Please update any risk on the centralized wiki page - Frankfurt Risks

  • Resources

Fill out the Resources Committed to the Release centralized page.

  • Release Milestone

...