History

Andrey Kurilin 17d9b3e3c0 Fix building docs I guess the root cause is https://sourceforge.net/p/docutils/bugs/353/ Change-Id: Iedbb6d41ff1a38549766a1ca7b779c86c41f2792		2019-09-02 16:36:06 +03:00
..
ext	Fix building docs	2019-09-02 16:36:06 +03:00
feature_request	update documentation reference	2018-02-09 15:05:35 +08:00
release_notes	Prepare to Rally 1.0.0 release	2018-06-20 19:02:05 +03:00
source	Allow regular expressions in skip-list	2019-05-29 14:10:29 +01:00
specs	fix typos	2018-06-21 17:42:46 +08:00
user_stories	update references to samples/deployments to point to openstack plugin repo	2019-01-14 14:47:46 +00:00
README.rst	update documentation reference	2018-02-09 15:05:35 +08:00
requirements.txt	[ci] Manage tox job manually	2018-10-26 16:33:15 +03:00

README.rst

Content of doc directory

This directory contains everything that is related to documentation and bureaucracy. You can find here 4 subdirectories:

feature_request

If some use case is not covered by Rally, it is the right place to request it. To request new feature you should just explain use case on high level. Technical details and writing code are not required at all.

source

Source of documentation. Latest version of documentation.

specs

Specs are detailed description of proposed changes in project. Usually they answer on what, why, how to change in project and who is going to work on change.

user_stories

Place where you can share any of Rally user experience. E.g. fixing some bugs, measuring performance of different architectures or comparing different hardware and so on..

release_notes

The latest.rst contains new features and API changes of Rally's latest release. And you could find all old releases in archive.