Openflow Protocol Library: Boron: Release Plan

Contents

Introduction

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

Release Deliverables

NameDescription
Bugfix & moreBugfixing, performance improvement and other necessary changes (changes won't break freeze rules)

Release Milestones

MilestoneOffset 1 DateDeliverables
M13/17/2016
NameStatusDescription
Intent to participateDoneIntent to participate in Boron Simultaneous Release
Project Lead electedDoneOpenflowJava Project Lead election
Test Contact specifiedDoneOpenflowJava Test Contact announce
Candidate Release PlanDoneCandidate Release Plan
M24/21/2016
NameStatusDescription
Release PlanDoneFinal Release Plan
Project ChecklistDoneProject Checklist completed
OpenDaylight CIDoneOpenDaylight CI infrastructure usage for system test
Project acknowledgedDoneProject acknowledged from all projects that it depends on.
M35/19/2016
NameStatusDescription
Functionality FreezeDoneFinal list of externally consumable APIs defined and documented
Karaf Features definedDoneKaraf Features defined
Documentation StartedDoneIdentified the kinds of documentation to be provided, created AsciiDoc files for them with outlines,

and committed those files in an appropriate location

Integration & System TestWaiverSimple system test on a karaf distribution with the project's recommended features installed
M46/16/2016
NameStatusDescription
API FreezeDone
Draft documentationDoneGoal of draft documentation done
Maven central requirementsDoneMeet the requirements to be included in maven central
Feature Test ContinuesWaiverSW configuration and resources required for system test installed
M59/21/2016
NameStatusDescription
Code FreezeDone
Stability branchDoneStability branch, i.e., stable/beryllium, must be cut and local project versions bumped on master

to avoid overwriting beryllium SNAPSHOTS

String FreezeDoneAll externally visible strings frozen to allow for translation & documentation
Documentation CompleteDoneOnly editing and and enhancing should take place after this point.
Feature Test CompleteDoneFeature Test Complete
RC08/11/2016
NameStatus
Release Candidate 0
RC18/18/2016
NameStatus
Release Candidate 1
RC28/25/2016
NameStatus
Release Candidate 2
RC39/1/2016
NameStatusDescription
Bugfix & more
Bugfixing, performance improvement and other necessary / desired changes
Release Review
Release Review
Release Candidate 3
Formal Release9/8/2016
NameStatusDescription
Formal Boron Release

Boron OF Library
Delivery of latest OF Protocol Java Library
Release patch
Release patch to the stable/boron branch and bump versions
SR1 Release10/6/2016
NameStatusDescription
Release patch
Release patch to the stable/boron branch and bump versions
SR2 Release11/17/2016
NameStatusDescription
Release patch
Release patch to the stable/boron branch and bump versions
SR3 Release2/16/2017
NameStatusDescription
Release patch
Release patch to the stable/boron branch and bump versions
SR4 Release5/18/2017
NameStatusDescription
Release patch
Release patch to the stable/boron branch and bump versions

Externally Consumable APIs

Short NameDescriptionType (at M2)Type (at M3)Type (release)ContractSupporting Code
openflowjava-apiData Transfer Objects + notification/rpc interfacesStable.openflowjava/openflow-protocol-api/src/main/yangodl-openflowjava-protocol
openflowjava-spiSwitchConnectionProvider - ofjava entry pointStable.openflowjava/openflow-protocol-spi/src/main/java/org.opendaylight.openflowjava.protocol.spi.connectionodl-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 ProjectAPI NameNeeded ByAcknowledged?Description
XYZ Projectcall_meM4NoThis 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