openstack
/
governance
Code Issues Proposed changes

remove naming timebox restriction 

There is no reason to hold off on naming releases one we know their
location. And holding off on release naming is more likely to create
confusion where the dev community just picks a placeholder, uses it in
communication, and that placeholder is wrong later.

Especially as projects are now moving into a phase of planning for
multiple releases in advance for larger efforts, the current
restriction just adds confusion and cleanup work later.

Change-Id: Ife143447ff4a6d2d85260fd9d889853863eff272
This commit is contained in:
Sean Dague 2015-10-08 07:45:51 -04:00
parent 604b7c8dc8
commit c194944dcd
1 changed files with 1 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
reference/release-naming.rst
View File

@ -26,8 +26,7 @@ following steps:
#. The process to chose the name for a release begins once the
location of the design summit of the release to be named is
announced and no sooner than the opening of development of the
previous release.
announced.
#. Anyone may propose a name that matches the `Release Name
Criteria`_. Proposed names should be added to a page on the