Cinder Project Releases

The Cinder project follows the OpenStack 6 month development cycle, at the end of which a new stable branch is created from master, and master becomes the development branch for the next development cycle.

Because many OpenStack consumers don’t move as quickly as OpenStack development, we backport appropriate bugfixes from master into the stable branches and create new releases for consumers to use … for a while. See the Stable Branches section of the OpenStack Project Team Guide for details about the timelines.

What follows is information about the Cinder project and its releases.

Where Stuff Is

The Cinder Project Deliverables

The Code Repositories

Review Dashboards for Releases

All Cinder Project Releases

How Stuff Works

Releases from Master

Releases from master for cinder follow the ‘cycle-with-rc’ release model.

  • The ‘cycle-with-rc’ model describes projects that produce a single release at the end of the cycle, with one or more release candidates (RC) close to the end of the cycle and optional development milestone betas published on a per-project need.

Releases from master for os-brick, cinderlib, and the clients follow the ‘cycle-with-intermediary’ release model.

  • The ‘cycle-with-intermediary’ model describes projects that produce multiple full releases during the development cycle, with a final release to match the end of the cycle.

  • os-brick has a deliverable type of ‘library’

  • python-cinderclient and python-brick-cinderclient-ext have a deliverable type of ‘client-library’

  • cinderlib has a deliverable type of ‘trailing’

    • The final cinderlib release for a cycle must occur no later than 3 months after the coordinated OpenStack release of cinder.

Releases from master for cinder-tempest-plugin follow the ‘cycle-automatic’ scheme.

  • No stable branches are created.

  • Released automatically at the end of each cycle, or on-demand.

Releases from master for rbd-iscsi-client follow the ‘independent’ scheme.

  • No stable branches are created.

  • Released on demand whenever necessary because it has to track ceph development more than openstack development.

For more information about the release models and deliverable types:


All Cinder project deliverables (except cinder-tempest-plugin and rbd-iscsi-client) follow the OpenStack stable branch policy. Briefly,

  • The stable branches are intended to be a safe source of fixes for high impact bugs and security issues which have been fixed on master since a given release.

  • Stable branches are cut from the last release of a given deliverable, at the end of the common 6-month development cycle.

Only members of the cinder-stable-maint gerrit group have +2 powers on patches proposed to stable branches. This is a subset of cinder-core plus the OpenStack-wide stable-maint-core team.

While anyone may propose a release, releases must be approved by the OpenStack Release Managers.