rally/doc
Andrey Kurilin 7642d345bf Fix pep8 job according to latest set of rules
+ fix py34

Change-Id: Ie43ca6ce18928fc8a7c41fae916d44909308de70
2020-01-03 16:14:10 +02:00
..
ext Fix pep8 job according to latest set of rules 2020-01-03 16:14:10 +02: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 Remove redudant 'be' 2019-11-19 09:47:47 +01:00
specs Update the community page. 2019-12-03 10:09:22 +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

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.