Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: For bugs, Amsterdam only on this page

...

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQuerystatus != Closed AND status != Done AND project != "Sandbox Project" AND project = POLICY and Type = EPIC and fixVersion = 'Amsterdam Release' ORDER BY priority DESC, updated DESC
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

...

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

...

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

...

List the API this release is expecting from other releases.
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.

...

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject=POLICY and issuetype in (bug) and fixVersion='Amsterdam Release'
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

...

Resources

Fill out and provide a link toward the Resources Committed to the Release centralized page.

Release Milestone

The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.

...

The project team comply with the ONAP Charter.

Release Key Facts

Fill out and provide a link toward the centralized Release Artifacts.