Skip to end of banner
Go to start of banner

Openflow Protocol Library: Beryllium: Release Plan

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Contents

Release Deliverables

NameDescription
Openflow model updateModel updated in order to support removal of openflow structures from controller - common openflowjava <-> openflowplugin structures will be introduced to increase performance
Bugfix & moreBugfixing, performance improvement and other necessary / desired changes (changes won't break freeze rules)

Release Milestones

MilestoneOffset 1 DateDeliverables
M112/18/2014
NameStatusDescription
Intent to participateDoneIntent to participate in Lithium Simultaneous Release
Project Lead electedDoneOpenflowJava Project Lead election
Test Contact specifiedDoneOpenflowJava Test Contact announce
Candidate Release PlanDoneCandidate Release Plan
M21/29/2015
NameStatusDescription
Release PlanDoneFinal Release Plan
Project ChecklistDoneProject Checklist completed
OpenDaylight CIDoneOpenDaylight CI infrastructure usage for system test
Openflow model updateWaiting for OF Plugin - deliverable moved to M3Model update
M33/05/2015
NameStatusDescription
Openflow model updateDoneModel update
Functionality FreezeDoneFinal list of externally consumable APIs defined and documented
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 TestDoneSimple system test on a karaf distribution with the project's recommended features installed
M44/02/2015
NameStatus
API FreezeDone
M54/30/2015
NameStatusDescription
Stability branchDoneStability branch, i.e., stable/lithium, must be cut and local project versions bumped on master

to avoid overwriting lithium SNAPSHOTS

String FreezeDoneAll externally visible strings frozen to allow for translation & documentation
Documentation CompleteDoneOnly editing and and enhancing should take place after this point.
Code FreezeDone
RC0N/A
NameStatus
Release Candidate 0Tested
RC1N/A
NameStatus
Release Candidate 1Tested
RC2N/A
NameStatus
Release Candidate 2Tested
RC3N/A
NameStatusDescription
Bugfix & moreDoneBugfixing, performance improvement and other necessary / desired changes
Release ReviewDoneRelease Review
Release Candidate 3Tested
Formal ReleaseN/A
NameStatusDescription
Formal Lithium ReleaseDone
Lithium OF LibraryDoneDelivery of new features inside OF Protocol Java Library
Release patchDoneRelease patch to the stable/lithium branch and bump versions
SR1 ReleaseN/A
NameStatusDescription
Release patch
Release patch to the stable/lithium branch and bump versions
SR2 ReleaseN/A
NameStatusDescription
Release patch
Release patch to the stable/lithium branch and bump versions

Externally Consumable APIs

  • openflow-protocol-api
  • openflow-protocol-spi

Expected Dependencies on Other Projects

Compatibility with Previous Releases

Incompatibility due to model update - common openflowjava and openflowplugin models will be designed and used.

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)

Test Tools Requirements

  • Testing is done in form of Java unit tests and integration tests. Reporting is provided by Jenkins.

Other

  • No labels