governance

Go to file

armando-migliaccio 8957cf7613 Add assert:supports-upgrade tag to Neutron

Based on requirements defined in [1], I believe that is
a fair statement to claim cold upgrades support for Neutron.

Rolling upgrades are not too far off, but not within our reach
to allow us to claim assert:support-rolling-upgrade, just yet.
This is mainly because of lack of full stack integration testing
with services arranged in a mid-upgrade manner. This is planned
for Mitaka, and I count to reconsider adding the latter tag in
time for the release.

[1] http://governance.openstack.org/reference/tags/assert_supports-upgrade.html#requirements

Change-Id: I691325fe5f8562fb59239ecde75f0992a53d599e

2015-11-16 23:54:52 -08:00

doc/source

change projects schema to support more ptl contact data

2015-10-13 20:05:21 +00:00

pre-history

Add some pre-history meeting summaries

2013-11-11 09:08:57 -06:00

reference

Add assert:supports-upgrade tag to Neutron

2015-11-16 23:54:52 -08:00

resolutions

stackforge retirement: make workflow reqs+cla clearer

2015-10-05 19:12:43 +09:00

tools

Merge "teamstats: Add stats related to team size."

2015-08-12 12:07:41 +00:00

.gitignore

ignore files created by pbr during build

2015-05-23 08:09:26 -07:00

.gitreview

Added .gitreview

2013-08-30 16:00:06 +00:00

README.rst

provide infrastructure for publishing docs to html

2014-01-07 15:29:11 -05:00

setup.cfg

update doc build requirements

2014-10-27 13:44:50 -04:00

setup.py

provide infrastructure for publishing docs to html

2014-01-07 15:29:11 -05:00

test-requirements.txt

Build list of teams from YAML file

2015-02-24 18:15:04 -05:00

tox.ini

Ensure that reference/projects.yaml is sorted

2015-07-29 21:02:12 +02:00

README.rst

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.