Go to file
Sean McGinnis 1c862db6f9 Begin the 'V' release naming process
We have had several proposals for changing the release
naming process, but have yet to find one that has
agreement that would be better than the current process.

Until we decide on a new naming scheme, we should
continue the process in place. This kicks off the
naming for the V release that will be based on the
collaboration event that will take place in Vancouver
since we will no longer have a Summit event.

Name nominations will use the pattern we have established
and are detailed in:

https://wiki.openstack.org/wiki/Release_Naming/V_Proposals

Change-Id: Ibf3ebb585174aaf5e3e428ce0674f46aa8380dc2
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
2019-11-06 17:04:17 -06:00
2019-05-22 22:02:02 +08:00
2019-04-19 19:47:56 +00:00
2019-10-22 02:36:36 -04:00
2019-07-29 11:38:42 +08:00

openstack-governance

The repository https://opendev.org/openstack/governance/ contains OpenStack Technical Committee reference documents and tracks official resolutions voted by the committee. It also contains a library for accessing some of the machine-readable data in the repository.

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.

goals/

Documentation for OpenStack community-wide goals, organized by release cycle. These pages will be updated with project status info over time, and if goals are revised.

See https://governance.openstack.org/tc/ for details.

Description
OpenStack Technical Committee Decisions
Readme 44 MiB
Languages
Python 93.8%
DIGITAL Command Language 5.1%
Shell 0.9%
C++ 0.2%