3ed8ac0e93
Patch Ia56cba58c87aa48de3e8e3f3d28f6252f7dcd7c3 introduced a new role 'ensure-python' which checks for installed python version before our pre-run playbook can install not-default versions. Such change broke our py34 job. To continue checking Python 3.4 and ensure that everything is done as we wish let's do not use global 'tox' job and implement the custom one. The new rally-tox-base job checks tox.ini for required python version and installs it via 'apt'. Also, there is new post playbook which publishes the results of execution. Change-Id: Ia69d36670ff07079c82c9b1fef54d8ade62c7c7b |
||
|---|---|---|
| .. | ||
| ext | ||
| feature_request | ||
| release_notes | ||
| source | ||
| specs | ||
| user_stories | ||
| README.rst | ||
| requirements.txt | ||
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.