OpenStack Project Team Guide
Go to file
Thierry Carrez 6fe830e43a Add need for -stable-maint and -release groups
Release management assumes that all projects following a
cycle-with-milestones model will use a $PROJECT-release
team to review backports between RC1 and final.

It also assumes that all projects following the stable
policy will use a $PROJECT-stable-maint team.

So let's document that common practice!

NB: All teams already follow this pattern, except Kolla.
Once this merges (and depending on the conclusion of the
discussion around a deploytools-centric stable policy
variant), I'll fix the Kolla exception accordingly.

Change-Id: I3870e8463c6374df17c74579e7332d659ae634ac
2017-10-27 15:12:39 +02:00
doc/source Add need for -stable-maint and -release groups 2017-10-27 15:12:39 +02:00
.gitignore Add .gitignore 2015-06-10 12:50:37 -07:00
.gitreview Added .gitreview 2015-05-28 04:26:27 +00:00
LICENSE Add initial sphinx project boilerplate 2015-06-08 17:40:27 -07:00
README.rst Add initial sphinx project boilerplate 2015-06-08 17:40:27 -07:00
requirements.txt switch to openstackdocstheme 2017-07-21 14:38:02 -04:00
setup.cfg turn on warning-is-error 2017-07-21 14:54:57 -04:00
setup.py Add initial sphinx project boilerplate 2015-06-08 17:40:27 -07:00
tox.ini Add initial sphinx project boilerplate 2015-06-08 17:40:27 -07:00

README.rst

OpenStack Project Team Guide

To build the guide, execute the following command:

$ tox

After running tox, the documentation will be available for viewing in HTML format in the doc/build/ directory.