Difference between revisions of "Release Naming"
(→"K" release cycle naming) |
m |
||
| Line 1: | Line 1: | ||
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. | 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''. | + | 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''. That exception was extended to other major landmarks and reference points. |
* Austin: The first design summit took place in Austin, TX | * Austin: The first design summit took place in Austin, TX | ||
Revision as of 11:31, 10 July 2014
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. That exception was extended to other major landmarks and reference points.
- 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
- Juno: Juno is a locality in Georgia
Only single words with a maximum of 10 characters are good candidates for a name. Bonus points for sounding cool.
"K" release cycle naming
The following candidate names were cleared for public poll:
- Keryado: a small locality in Brittany
- Kilo: Paris (Sèvres, actually, but that's close enough) is home to the Kilogram, the only remaining SI unit tied to an artifact
- Kleber: A Paris avenue and subway station name, named after a French general from the French revolutionary wars
- Kourou: technically in France, but actually in French Guyana, South America. Home of the European space agency launch pad
- Kyoto: there is a microscopic 'Place de Kyoto' in Paris
