115 lines
5.4 KiB
ReStructuredText
115 lines
5.4 KiB
ReStructuredText
==============
|
|
Release Naming
|
|
==============
|
|
|
|
Each OpenStack development cycle has a code-name that is
|
|
proposed and chosen by the community. This name is frequently used in
|
|
preference to version numbers to refer to the release at the end of
|
|
the cycle. The process of choosing the name should be an enjoyable
|
|
activity for the community to mark the software development cycle, and
|
|
the name itself should be fun to use.
|
|
|
|
Because the name will become associated with OpenStack, and a
|
|
particular release, the process should consider potential issues of
|
|
trademark.
|
|
|
|
Release Naming Process
|
|
----------------------
|
|
|
|
The Technical Committee will designate an official to be responsible
|
|
for executing the release naming process, which consists of the
|
|
following steps:
|
|
|
|
#. The process to chose the name for a release begins once the
|
|
location of the summit that takes place during the development
|
|
cycle of the release to be named is announced.
|
|
|
|
#. Anyone may propose a name that matches the `Release Name
|
|
Criteria`_. Proposed names should be added to a page on the
|
|
OpenStack wiki.
|
|
|
|
#. The marketing community may identify any names of particular
|
|
concern from a marketing standpoint and discuss such issues
|
|
publicly on the Marketing mailing list. The marketing community
|
|
may produce a list of problematic items (with citations to the
|
|
mailing list discussion of the rationale) to the election official.
|
|
This information will be communicated during the election, but the
|
|
names will not be removed from the poll.
|
|
|
|
#. After the close of nominations, the election official will finalize
|
|
the list of proposed names and publicize it. In general, the
|
|
official should strive to make objective determinations as to
|
|
whether a name meets the `Release Name Criteria`_, but if
|
|
subjective evaluation is required, should be generous in
|
|
interpreting the rules. It is not necessary to reduce the list of
|
|
proposed names to a small number.
|
|
|
|
#. Once the list is finalized and publicized, a one-week period shall
|
|
elapse before the start of the election so that any names removed
|
|
from consideration because they did not meet the `Release Name
|
|
Criteria`_ may be discussed. Names erroneously removed may be
|
|
re-added during this period, and the Technical Committee may vote
|
|
to add exceptional names (which do not meet the standard criteria).
|
|
|
|
#. A Condorcet election is held to rank the names. The poll will be
|
|
public, with the voting URL communicated through OpenStack mailing-lists
|
|
(openstack, openstack-dev, openstack-operators, openstack-foundation).
|
|
The poll will include the names along with any links to mailing list
|
|
discussions provided by the marketing community.
|
|
|
|
#. The Foundation will perform a trademark check on the winning name.
|
|
If there is a trademark conflict, then the Foundation will proceed
|
|
down the ranked list of Condorcet results until a name without a
|
|
trademark conflict is found. This will be the selected name.
|
|
|
|
|
|
Release Name Criteria
|
|
---------------------
|
|
|
|
The following rules are designed to provide some consistency in the
|
|
pattern used to select release names, provide a fun challenge in
|
|
finding names that meet the criteria, and prevent unwieldy names from
|
|
being chosen.
|
|
|
|
#. Each release name must start with the letter of the ISO basic Latin
|
|
alphabet following the initial letter of the previous release,
|
|
starting with the initial release of "Austin". After "Z", the next
|
|
name should start with "A" again.
|
|
|
|
#. The name must be composed only of the 26 characters of the ISO
|
|
basic Latin alphabet. Names which can be transliterated into this
|
|
character set are also acceptable.
|
|
|
|
#. The name must refer to the physical or human geography of the
|
|
region encompassing the location of the OpenStack summit for
|
|
the corresponding release. The exact boundaries of the geographic
|
|
region under consideration must be declared before the opening of
|
|
nominations, as part of the initiation of the selection process.
|
|
|
|
#. The name must be a single word with a maximum of 10 characters.
|
|
Words that describe the feature should not be included, so "Foo
|
|
City" or "Foo Peak" would both be eligible as "Foo".
|
|
|
|
Names which do not meet these criteria but otherwise sound really cool
|
|
should be added to a separate section of the wiki page and the TC may
|
|
make an exception for one or more of them to be considered in the
|
|
Condorcet poll. The naming official is responsible for presenting the
|
|
list of exceptional names for consideration to the TC before the poll
|
|
opens.
|
|
|
|
Polls
|
|
-----
|
|
|
|
======= ============= ================ ========== ========== ==================
|
|
Release Coordinator Nominations Open Poll Open Poll Close Geographic Region
|
|
======= ============= ================ ========== ========== ==================
|
|
M Monty Taylor 2015-06-01 2015-06-08 2015-06-15 N/A
|
|
N Monty Taylor 2015-11-08 2015-11-30 2015-12-07 Texas Hill Country
|
|
O Monty Taylor 2015-11-08 2015-11-30 2015-12-07 Catalonia
|
|
P Monty Taylor 2016-06-22 2016-07-06 2016-07-13 New England
|
|
Q Monty Taylor 2016-06-22 2016-07-06 2016-07-13 New South Wales
|
|
R Monty Taylor 2017-03-22 2017-04-05 2017-04-12 British Columbia
|
|
S Paul Belanger 2018-02-21 2018-03-14 2018-03-21 Berlin
|
|
T Tony Breeds 2018-09-15 2018-10-15 2018-10-22 Colorado
|
|
======= ============= ================ ========== ========== ==================
|