|Havana||Under development||Due||Oct 17, 2013|
|Grizzly||Current stable release, security-supported||2013.1||Apr 4, 2013|
|2013.1.1||May 9, 2013|
|2013.1.2||Jun 6, 2013|
|Folsom||Security-supported||2012.2||Sep 27, 2012|
|2012.2.1||Nov 29, 2012|
|2012.2.2||Dec 13, 2012|
|2012.2.3||Jan 31, 2013|
|2012.2.4||Apr 11, 2013|
|Essex||EOL||2012.1||Apr 5, 2012|
|2012.1.1||Jun 22, 2012|
|2012.1.2||Aug 10, 2012|
|2012.1.3||Oct 12, 2012|
|Diablo||EOL||2011.3||Sep 22, 2011|
|2011.3.1||Jan 19, 2012|
|Cactus||Deprecated||2011.2||Apr 15, 2011|
|Bexar||Deprecated||2011.1||Feb 3, 2011|
|Austin||Deprecated||2010.1||Oct 21, 2010|
The Vulnerability Management team provides advisories with patches for the two previous releases of OpenStack. Older releases may or may not be supported by their stable maintenance teams, see below.
Stable branches are centralized efforts to maintain bugfixes and vulnerability fixes for released OpenStack project versions in ready-to-use branches.
Current stable release (Grizzly)
The current stable release branches are maintained by the openstack-stable-maint team. This team makes sure security fixes are included in the stable branch by the time security advisories go out.
The Folsom stable branch (stable/folsom) is maintained by the openstack-stable-maint team. This team makes sure security fixes are included in the stable branch by the time security advisories go out.
The Essex stable branch (stable/essex) was maintained by the openstack-essex-maint community team.
The Diablo stable branch (stable/diablo) was maintained by the openstack-diablo-maint community team.