Name	Status	Description
Functionality Freeze	Done	Final list of externally consumable APIs defined and documented
Karaf Features defined	Done	Karaf Features defined
Documentation Started	Done	Identified the kinds of documentation to be provided, created AsciiDoc files for them with outlines, and committed those files in an appropriate location
Integration & System Test	Done	Simple system test on a karaf distribution with the project's recommended features installed

M4

11/12/2015

Name	Status	Description
API Freeze	Done	All external consumable
Draft documentation	Done	Goal of draft documentation done
Maven central requirements	Done	Meet the requirements to be included in maven central
Feature Test Continues	Done	SW configuration and resources required for system test installed

M5

12/17/2015

Name	Status	Description
Code Freeze	Done
Stability branch	Done	Stability branch, i.e., stable/beryllium, must be cut and local project versions bumped on master to avoid overwriting beryllium SNAPSHOTS
String Freeze	Done	All externally visible strings frozen to allow for translation & documentation
Documentation Complete	Done	Only editing and and enhancing should take place after this point.
Feature Test Complete	Done	Feature Test Complete

RC0

1/7/2016

Name	Status
Release Candidate 0

RC1

1/14/2016

Name	Status
Release Candidate 1

RC2

1/21/2016

Name	Status
Release Candidate 2

RC3

1/28/2016

Name	Status	Description
Bugfix & more		Bugfixing, performance improvement and other necessary / desired changes
Release Review		Release Review
Release Candidate 3

Formal Release

2/4/2016

Name	Status	Description
Formal Beryllium Release
Beryllium OF Library		Delivery of new features inside OF Protocol Java Library
Release patch		Release patch to the stable/beryllium branch and bump versions

SR1 Release

3/17/2016

Name	Status	Description
Release patch		Release patch to the stable/beryllium branch and bump versions

SR2 Release

4/28/2016

Name	Status	Description
Release patch		Release patch to the stable/beryllium branch and bump versions

SR3 Release

7/28/2016

Name	Status	Description
Release patch		Release patch to the stable/beryllium branch and bump versions

SR4 Release

10/20/2016

Name	Status	Description
Release patch		Release patch to the stable/beryllium branch and bump versions

Externally Consumable APIs

Short Name	Description	Type (at M2)	Type (at M3)	Contract	Supporting Code
register-user	Register a user to the user repository	tentative	Provisional	nemo/nemo-api/src/main/yang/nemo-intent.yang	org.opendaylight.nemo.nemo-api
begin-transaction	Begin a transaction for the user	tentative	Provisional	nemo/nemo-api/src/main/yang/nemo-intent.yang	org.opendaylight.nemo.nemo-api
end-transaction	Commit the user's current transaction	tentative	Provisional	nemo/nemo-api/src/main/yang/nemo-intent.yang	org.opendaylight.nemo.nemo-api
language-style-nemo-request	Create, update or delete an intent of a user through an NEMO statement	tentative	Provisional	nemo/nemo-api/src/main/yang/nemo-intent.yang	org.opendaylight.nemo.nemo-api
structure-style-nemo-update	Create or update all or a part of the user's intents which are described as json or xml format	tentative	Provisional	nemo/nemo-api/src/main/yang/nemo-intent.yang	org.opendaylight.nemo.nemo-api
structure-style-nemo-delete	Delete some intents of a user from the user repository	tentative	Provisional	nemo/nemo-api/src/main/yang/nemo-intent.yang	org.opendaylight.nemo.nemo-api
advanced-nemo-query	Query some intents of a user from the user repository according to several advanced query conditions	tentative	Provisional	nemo/nemo-api/src/main/yang/nemo-intent.yang	org.opendaylight.nemo.nemo-api

Expected Dependencies on Other Projects

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.dlux	dlux	M1	No (as link to Other Project Release Plan)	Legacy dependency
org.opendaylight.usc	usc	M2	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
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...)

Name	Description
NEMO Engine	The core NEMO engine
OF Renderer	OpenFlow Renderer
NEMO UI	User interface integrated into DLUX

OpenDaylight

NEMO: Beryllium: Release Plan

Contents

Release Deliverables

Release Milestones