keystone-specs/specs/keystone/mitaka
Steve Martinelli 9253062353 Reorder the specs repo
* create a project level folder for each project
* create folders for each release within the project
* move the backlog folder to keystone
* place the keystoneclient/keystonemiddleware specs in
  their correct release
* collapse the "implemented" specs onto the landing page

probably best to review the generated web page

Change-Id: I6d70cf5a7df190eb7e030df53ed8790510dc33f8
2016-03-31 01:57:42 -04:00
..
add-isdomain-to-token.rst Reorder the specs repo 2016-03-31 01:57:42 -04:00
bootstrap.rst Reorder the specs repo 2016-03-31 01:57:42 -04:00
domain-config-default.rst Reorder the specs repo 2016-03-31 01:57:42 -04:00
domain-specific-roles.rst Reorder the specs repo 2016-03-31 01:57:42 -04:00
federated-user-mapping-using-group-ids.rst Reorder the specs repo 2016-03-31 01:57:42 -04:00
implied-roles.rst Reorder the specs repo 2016-03-31 01:57:42 -04:00
is_admin_project.rst Reorder the specs repo 2016-03-31 01:57:42 -04:00
list-assignment-names.rst Reorder the specs repo 2016-03-31 01:57:42 -04:00
list-assignment-tree.rst Reorder the specs repo 2016-03-31 01:57:42 -04:00
list-role-assignments-performance.rst Reorder the specs repo 2016-03-31 01:57:42 -04:00
remove-role-metadata.rst Reorder the specs repo 2016-03-31 01:57:42 -04:00
reseller.rst Reorder the specs repo 2016-03-31 01:57:42 -04:00
shadow-users.rst Reorder the specs repo 2016-03-31 01:57:42 -04:00
totp-auth.rst Reorder the specs repo 2016-03-31 01:57:42 -04:00
tree-deletion.rst Reorder the specs repo 2016-03-31 01:57:42 -04:00
url-safe-names.rst Reorder the specs repo 2016-03-31 01:57:42 -04:00