c194944dcd

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 repository contains OpenStack Technical Committee reference documents and tracks official resolutions voted by the committee.
Directory structure:
- reference/
Reference documents which need to be revised over time. Some motions will just directly result in reference doc changes.
- resolutions/
When the motion does not result in a change in a reference doc, it can be expressed as a resolution. Those must be named YYYYMMDD-short-name with YYYYMMDD being the proposal date in order to allow basic sorting.
See https://wiki.openstack.org/wiki/Governance/TechnicalCommittee for details.
Description
Languages
Python
95.3%
DIGITAL Command Language
3.5%
Shell
1%
C++
0.2%