History

Amy Ge 06cd90e39c Improve plugin sample and corresponding 'creating a plugin' tutorial The scenario_plugin.py was updated, however, the documentation still has the old instruction for creating a plugin. Let's update that in- struction. Let's also add 'required_services' and 'required_platform' in the sample to make it more complete. Change-Id: I6d36ea51a3ee32b94ab296c77195ee22652f40ec		2017-06-20 16:12:20 -07:00
..
ext	[docs] include required platforms of plugins	2017-06-16 13:27:34 +00:00
feature_request	Corrected the grammar mistake	2017-03-28 12:14:26 +00:00
release_notes	add release notes for 0.9.0	2017-03-20 15:28:16 +02:00
source	Improve plugin sample and corresponding 'creating a plugin' tutorial	2017-06-20 16:12:20 -07:00
specs	[spec] OSProfiler integration in Rally	2017-04-24 23:50:10 +03:00
user_stories	[docs] reduce sphinx warnings	2017-02-07 15:28:53 +02:00
README.rst	Change deployment model schema	2016-03-28 17:20:46 +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.