bf72edf41b
Prepare for deployment refactoring. Add migration to add column credentials to deployment model and drop users and admin columns. Add tests for migrations and walk mixin for it implementation. Add documentation about autogeneration of migrations. Add possibility to make batch rendering for alembic autogeneration. Change-Id: I5958a96671d2fb111533c09feb462b4dcd7483b9 |
||
|---|---|---|
| .. | ||
| ext | ||
| feature_request | ||
| release_notes | ||
| source | ||
| specs | ||
| user_stories | ||
| 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.