Difference between revisions of "Release Naming"

Revision as of 13:17, 12 December 2013

OpenStack releases are numbered using a YYYY.N time-based scheme. For example, the first release of 2012 will have the 2012.1 version number. During the development cycle, the release is identified using a codename. Those codenames are ordered alphabetically: Austin was the first release, Bexar is the second, Cactus the third, etc.

These codenames are chosen by popular vote using the basic Launchpad poll feature over the ~openstack group. Codenames are cities or counties near where the corresponding OpenStack design summit took place. An exception (called the Waldon exception) is granted to elements of the state flag that sound especially cool.

• Austin: The first design summit took place in Austin, TX
• Bexar: The second design summit took place in San Antonio, TX (Bexar county).
• Cactus: Cactus is a city in Texas
• Diablo: Diablo is a city in the bay area near Santa Clara, CA
• Essex: Essex is a city near Boston, MA
• Folsom: Folsom is a city near San Francisco, CA
• Grizzly: Grizzly is an element of the state flag of California (design summit takes place in San Diego, CA)
• Havana: Havana is an unincorporated community in Oregon
• Icehouse: Ice House is a street in Hong Kong

Only single words with a maximum of 10 characters are good candidates for a name. Bonus points for sounding cool.

"J" release cycle naming

The next OpenStack summit will happen in Atlanta (Georgia, USA). Here are the proposed candidates:

• Jackson (county & municipality)
• Jakin (municipality)
• Jefferson (county & municipality)
• Jekyll (island)
• Jersey (municipality)
• Jesup (municipality)
• Johnson (county)
• Jones (county)
• Jonesboro (municipality)
• Juno (locality)

Rejected options

• Jasper (county & municipality) (confusion with jasper soft)
• Jenkins (county) (confusion with Jenkins !)
• Jeremiah (name of farm near Alma, Georgia) (no need to extend the rules that far to find good candidates)