Watcher Specifications
Go to file
OpenDev Sysadmins 3ce6a9cb2c OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:

http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html

Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.
2019-04-19 19:47:52 +00:00
doc/source Solve the error: 'Sphinx' object has no attribute 'info' 2019-04-04 17:44:18 +08:00
priorities Add Train priorities 2019-04-15 08:42:48 +02:00
specs Merge "Add spec for file based metric map" 2019-04-11 02:46:45 +00:00
tests Provide a more dynamic Actions management solution 2016-01-08 10:53:54 +01:00
.gitignore Add Stein series and move approved Rocky specs as implemented 2018-09-12 18:03:05 +00:00
.gitreview OpenDev Migration Patch 2019-04-19 19:47:52 +00:00
.stestr.conf Switch to stestr 2018-07-10 11:22:34 +07:00
.zuul.yaml import zuul job settings from project-config 2018-08-22 18:13:12 +09:00
LICENSE Setup watcher-specs repository 2015-11-10 06:28:39 -06:00
README.rst Update links in README 2017-08-04 11:13:23 +08:00
requirements.txt Solve the error: 'Sphinx' object has no attribute 'info' 2019-04-04 17:44:18 +08:00
setup.cfg Change openstack-dev to openstack-discuss 2018-12-04 17:30:29 +08:00
setup.py Setup watcher-specs repository 2015-11-10 06:28:39 -06:00
test-requirements.txt Switch to stestr 2018-07-10 11:22:34 +07:00
tox.ini Remove stestr from requirements.txt 2018-12-05 13:28:49 +03:00

README.rst

Team and repository tags

image

README

Watcher Specifications

This git repository is used to hold approved design specifications for additions to the Watcher project. Reviews of the specs are done in gerrit, using a similar workflow to how we review and merge changes to the code itself. For specific policies around specification review, refer to the end of this document.

The layout of this repository is:

specs/<release>/

Where there are two sub-directories:

specs/<release>/approved: specifications approved, but not yet implemented specs/<release>/implemented: implemented specifications