Contents
Introduction
This is only draft release plan - it might change until M2.
Release Deliverables
Name | Description |
---|
Bugfix & more | Bugfixing, performance improvement and other necessary changes (changes won't break freeze rules) |
Release Milestones
Milestone | Offset 1 Date | Deliverables |
---|
M1 | 3/17/2016 | Name | Status | Description |
---|
Intent to participate | Done | Intent to participate in Boron Simultaneous Release | Project Lead elected | Done | OpenflowJava Project Lead election | Test Contact specified | Done | OpenflowJava Test Contact announce | Candidate Release Plan | Done | Candidate Release Plan |
|
M2 | 4/21/2016 | Name | Status | Description |
---|
Release Plan | Done | Final Release Plan | Project Checklist | Done | Project Checklist completed | OpenDaylight CI | Done | OpenDaylight CI infrastructure usage for system test | Project acknowledged | Done | Project acknowledged from all projects that it depends on. |
|
M3 | 5/19/2016 | 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 | Waiver | Simple system test on a karaf distribution with the project's recommended features installed |
|
M4 | 6/16/2016 | Name | Status | Description |
---|
API Freeze | Done |
| Draft documentation | Done | Goal of draft documentation done | Maven central requirements | Done | Meet the requirements to be included in maven central | Feature Test Continues | Waiver | SW configuration and resources required for system test installed |
|
M5 | 9/21/2016 | 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 | 8/11/2016 | Name | Status |
---|
Release Candidate 0 |
|
|
RC1 | 8/18/2016 | Name | Status |
---|
Release Candidate 1 |
|
|
RC2 | 8/25/2016 | Name | Status |
---|
Release Candidate 2 |
|
|
RC3 | 9/1/2016 | Name | Status | Description |
---|
Bugfix & more |
| Bugfixing, performance improvement and other necessary / desired changes | Release Review |
| Release Review | Release Candidate 3 |
|
|
Formal Release | 9/8/2016 | Name | Status | Description |
---|
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 Release | 10/6/2016 | Name | Status | Description |
---|
Release patch |
| Release patch to the stable/boron branch and bump versions |
|
SR2 Release | 11/17/2016 | Name | Status | Description |
---|
Release patch |
| Release patch to the stable/boron branch and bump versions |
|
SR3 Release | 2/16/2017 | Name | Status | Description |
---|
Release patch |
| Release patch to the stable/boron branch and bump versions |
|
SR4 Release | 5/18/2017 | Name | Status | Description |
---|
Release patch |
| Release patch to the stable/boron branch and bump versions |
|
Externally Consumable APIs
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 |
---|
XYZ Project | call_me | M4 | No | This is an example to request API supported |
- 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