Openflow Protocol Library: Boron: Release Plan

Openflow Protocol Library: Boron: Release Plan

Contents

Introduction

This is only draft release plan - it might change until M2.

Release Deliverables

Name

Description

Name

Description

Bugfix & more

Bugfixing, performance improvement and other necessary changes (changes won't break freeze rules)

Release Milestones

Milestone

Offset 1 Date

Deliverables

Milestone

Offset 1 Date

Deliverables

M1

3/17/2016





M2

4/21/2016





M3

5/19/2016





M4

6/16/2016





M5

9/21/2016





RC0

8/11/2016





RC1

8/18/2016





RC2

8/25/2016





RC3

9/1/2016





Formal Release

9/8/2016





SR1 Release

10/6/2016





SR2 Release

11/17/2016





SR3 Release

2/16/2017





SR4 Release

5/18/2017





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

openflowjava-api

Data Transfer Objects + notification/rpc interfaces

Stable.

openflowjava/openflow-protocol-api/src/main/yang

odl-openflowjava-protocol

openflowjava-spi

SwitchConnectionProvider - ofjava entry point

Stable.

openflowjava/openflow-protocol-spi/src/main/java/org.opendaylight.openflowjava.protocol.spi.connection

odl-openflowjava-protocol



Expected Dependencies on Other Projects

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