/
USC: Boron: Release Plan

USC: Boron: Release Plan

Contents

Release Deliverables

Name

Description

Name

Description

Release Milestones

Milestone

Offset 1 Date

Deliverables

Milestone

Offset 1 Date

Deliverables

M1







M2







M3







M4







M5







RC0







RC1







RC2







RC3







Formal Release







SR1 Release







SR2 Release







SR3 Release







SR4 Release







Externally Consumable APIs

Short Name

Description

Type (at M2)

Type (at M3)

Type (release)

Contract

Supporting Code

Short Name

Description

Type (at M2)

Type (at M3)

Type (release)

Contract

Supporting Code

usc-channel

Model and RPC

Stable

Stable



usc/usc-channel-api/src/main/yang

org.opendaylight.usc.channel

Expected Dependencies on Other Projects

Providing Project

Deliverable Name

Needed By

Acknowledged?

Description

Providing Project

Deliverable Name

Needed By

Acknowledged?

Description

org.opendaylight.odlparent.odlparent

odlparent

M1

No
(as link to Other Project Release Plan)

Legacy dependency

org.opendaylight.yangtools.yang-binding,

yangtools

M1

No
(as link to Other Project Release Plan)

Legacy dependency

org.opendaylight.controller.netconf-config-dispatcher

netconf

M1

No
(as link to Other Project Release Plan)

Legacy dependency

org.opendaylight.dlux

dlux

M1

No
(as link to Other Project Release Plan)

Legacy dependency

Expected Incompatibilities with Other Projects

Compatibility with Previous Releases

Removed APIs and/or Functionality

Deprecated APIs and/or Functionality

Changed APIs and/or Functionality

Themes and Priorities

Requests from Other Projects

For each API / feature request, the requesting project MUST:

  • open Enhancement bug in Bugzilla describing request with Issue Type: Improvement, Change Request or New Feature

  • create an entry as described in Release Plan - Request template, which will also contain number / link to the bug. After creating the entry, the requesting project MUST:

send an e-mail to release@lists.opendaylight.org (mandated by Simultaneous Release)and both projects' dev lists using this template (mandated by Simultaneous Release)

Requesting Project

API Name

Needed By

Acknowledged?

Description

Requesting Project

API Name

Needed By

Acknowledged?

Description

XYZ Project

call_me

M4

No

This is an example to request API supported



Test Tools Requirements

  • Please specify if the project will run System Test (ST) inside OpenDaylight cloud

  • In case affirmative please enumerate any test tool (mininet, etc...) you think will be required for testing your project

    • The goal is to start test tools installation in rackspace as soon as possible

  • In case negative be aware you will be required to provide System Test (ST) reports upon any release creation (weekly Release, Release Candidate, Formal Release, etc...)

Other

Related content