Steven Hardy 5378de399f Adjust TripleO tags to reflect stable branches
Since liberty we've maintained stable branches for a number of repos that are
tied to a specific release. From Mitaka we've adopted the normal stable-branch
policy[1] and thus all branches will be maintained in accordance with this policy
from this point onwards (we can't backport anything to liberty that hasn't been
backported to mitaka, ergo all stable branches now follow the policy)

I've applied the stable:follows-policy tag to the following
repos where we maintain stable branches:

 tripleo-heat-templates
 instack-undercloud
 tripleo-common
 tripleo-puppet-elements
 puppet-tripleo

[1] http://lists.openstack.org/pipermail/openstack-dev/2016-March/090855.html

Change-Id: I77a0e9528042cfee63bdc0d00d6d363e6f8bdbc7
2016-12-12 08:09:57 -05:00
2013-08-30 16:00:06 +00:00
2014-10-27 13:44:50 -04:00
2016-10-18 14:09:41 +11:00

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.

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://wiki.openstack.org/wiki/Governance/TechnicalCommittee for details.

Description
OpenStack Technical Committee Decisions
Readme 42 MiB
Languages
Python 95.3%
DIGITAL Command Language 3.5%
Shell 1%
C++ 0.2%