Difference between revisions of "Release Naming"
| Line 41: | Line 41: | ||
|- | |- | ||
| Epping | | Epping | ||
| + | |- | ||
| + | | Elmwood | ||
|} | |} | ||
Note: Easthampton was excluded since it's 11-char long | Note: Easthampton was excluded since it's 11-char long | ||
Revision as of 00:59, 15 June 2011
Release Naming
OpenStack releases are numbered using a YYYY.N time-based scheme. For example, the first release of 2011 will have the 2011.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.
These codenames are chosen after a city or county near where the corresponding OpenStack design summit took place:
- Austin: The first design summit took place in Austin, TX
- Bexar: The second design summit took place in San Antonio, Bexar county.
- Cactus: Cactus is a city in Texas
- Diablo: Diablo is a city in the bay area near Santa Clara, CA
Only single words with a maximum of 10 characters are good candidates for a name. Bonus points for sounding cool.
E release naming
The E release name will be decided by popular vote using the basic Launchpad poll feature over the ~openstack group. Candidates are cities and counties near the next design summit place, starting with an E.
Looks like the next design summit will be in Boston, MA, so the candidates are:
| Candidate |
| Eastham |
| Easton |
| Edgartown |
| Egremont |
| Erving |
| Essex |
| Everett |
| Exeter |
| Epsom |
| Epping |
| Elmwood |
Note: Easthampton was excluded since it's 11-char long
