Release Frequency

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:

• February
• May
• August
• November

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.

Release Stages

Planning

 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.

Development

Developers submit code to Gerrit for review, and this code gets merged upon acceptance.  Learn more about the development process here.

Pre-release (Tagging release candidates)

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

Code freeze happens 15 days before the release date. This is subject to change.

Release

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.