You can view details of all ONOS Releases at:
ONOS releases have a 3 month time-based release cycle.
A new ONOS release will be available on the last day of the following four months:
Development items and bugs for each release are tracked through JIRA. If you are new to JIRA, you can learn more about using JIRA for ONOS on the ONOS JIRA wiki page.
At the beginning of each ONOS release cycle, proposed content for the release is discussed and prioritized. The proposed content i.e. the backlog (in Agile terminology) is tracked in JIRA.
Developers submit code to Gerrit for review, and this code gets merged upon acceptance. Learn more about the development process here.
Once all the development milestones are met and release-critical bugs are fixed, the first candidate for that release (RC1) is tagged. This RC1 build will be used as the final release, unless new release-critical issues are found in which case these are fixed and a new RC tag is applied to the subsequent build.
Code freeze happens 15 days before the release date. This is subject to change.
On release day (as described above in Release Frequency), the last tagged release candidate is re-versioned and published as the release on onosproject.org. You can find details on release versioning here.
Return to Releases section.
Each ONOS release will have the following version format:
During the development cycle and for easy identification post-release, each release is also identified by a "code" name in addition to the version. In keeping with the ONOS bird logo and the theme of openness and freedom, ONOS releases will be named after "Birds" in alphabetical order. Name of the first open source ONOS release is "Avocet" and is "EMu" for the next release in December, 2015.
For all releases after the February release, at the beginning of each release cycle, 3 names will be pre-selected by the Releases Steering team and provided to the ONOS Community via an online poll. The winning name will be used for the release. Only single word bird names with 10 characters or less are preferred for the release name but outside of these constraints, the Releases Steering Team and the Community have free rein.
The second release in 2016 will have the name of a bird starting with "g". Please email your suggestions for the August release name to onos-release-team@onosproject.org.
Release Name | Release Number | About the name | Release Date |
---|---|---|---|
Avocet | 1.0.0 | About the bird | Dec 5th, 2014 |
Blackbird | 1.1.0 | Feb 28th, 2015 | |
Cardinal | 1.2.0 | (Stanford "Cardinal" refers to the color, NOT the bird) | May 31st, 2015 |
Drake | 1.3.0 | About the bird | September 18th, 2015 |
Emu | TBD | About the bird | December 18th, 2015 |
Falcon | TBD | About the bird | TBD |
Return to Releases section.
Types of proposals:
You can find details on submitting a new feature proposal here.
Return to Releases section.
Branches
You can find details on versioning and naming of releases here.
Return to Releases section.
Release | Version | Release Date | Status |
---|---|---|---|
Avocet | 1.0.0 | December 5th, 2014 | Released |
Blackbird | 1.1.0 | February 28th, 2015 | Released |
Cardinal | 1.2.0 | May 31st, 2015 | Released |
Drake | 1.3.0 | September 18th, 2015 | Released |
Emu | TBD | December 18th, 2015 | Under Development |
Falcon | TBD | TBD | Proposed |
The status field can have one of the following values:
Return to Releases section.