Release Naming

Release Versioning and Tags

Each ONOS release will have the following version format:

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 will work for the Dec 5th, 2014 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
....

The first open source release on December 5th, 2014 will have the 1.0.0 version number. The next release in February, 2015 could be versioned either 1.1.0 or 2.0.0 based on the decision of the Technical Steering Team.

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. 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 "Blackbird" for the next release in February, 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.