Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.
| Table of Contents |
|---|
Release Dates
ONOS runs "train" based releases. That means whatever is ready to board the train, does so. Whatever isn't ready, has to wait for the next train. This enables us to have a very predictable release cadence making it easy to plan around. It also puts the responsibility on project owners to make sure they have features ready for the release. ONOS releases quarterly at the end of February, May, August, November. It is offset from the "normal" quarters because we all know that nothing happens for half of December. At the beginning of a release cycle, we have a planning meeting and two weeks before the end of the release we freeze integration of new features:
...
Format: <major>.<minor>.<revision>
- Either the <major> or the <minor> version will be incremented for each release. The Technical Steering Team will decide whether to increment the major or minor number for the release. This decision will depend on a number of different factors such as incompatibility with existing APIs etc.
- <revision> is incremented for a fix (or set of fixes) on a maintenance branch that justifies a new maintenance "release". Note: the revision number is optional when it is zero.
Example:
Here is how this versioning worked for the first open source release:
- 1.0.0rc1 - release candidate for 1.0.0. rc1 is a temporary tag that gets cleaned up after 1.0.0 is tagged final.
- 1.0.0 - Open source ONOS release on Dec 5th, 2014
- 1.0.1 - First maintenance release for 1.0.0
....
Release Naming
During the development cycle and for easy identification post-release, each release is also identified by a "code" name in addition to the version. Releases are named after birds because they are beautiful, found worldwide, are colorful and graceful, make beautiful music...and because they signify something taking flight into the wild blue yonder, something we advocate for SDN and NFV. Finally, and perhaps most importantly, birds work together in flight to reduce the load on each other so that they can fly long distances (for example, the V formation)...and, we hope that everyone in the ONOS community will adopt the same philosophy of helping each other to make ONOS great. We name them in alphabetical order.
Release Names and Versions
| Anchor | ||||
|---|---|---|---|---|
|
| Name | VERSION | Dates | Notes | About the name | Presentation |
|---|---|---|---|---|---|
| Hummingbird | 1.7.0 | Aug. 31, 2016 | About the bird | ||
| Goldeneye | 1.6.0 | Jun. 10, 2016 | Release Notes | About the bird | |
| Falcon | 1.5.0 | Mar. 10, 2016 | Release Notes | About the bird | pptx |
| Emu | 1.4.0 | Dec. 16, 2015 | About the bird | pptx | |
| Drake | 1.3.0 | Sept. 18, 2015 | About the bird | pptx | |
| Cardinal | 1.2.2 | Sept. 1, 2015 | (Stanford "Cardinal" refers to the color, NOT the bird) | ||
| 1.2.1 | June 25, 2015 | ||||
| 1.2.0 | June 5, 2015 | ||||
| Blackbird | 1.1.0 | Mar. 17, 2015 | |||
Avocet | 1.0.1 | Jan 21st, 2015 | About the bird | ||
| 1.0.0 | Dec 5th, 2014 |
To generate release detailed notes, use https://jira.onosproject.org/secure/ReleaseNote.jspa?projectId=10105
You can find details on versioning and naming of releases here.