openstack
/
keystone-specs
Code Issues Proposed changes

add a README file to the superseded spec folder 

Create a README file to modify when specs are marked as
superseded so we don't lose the reason why.

Also move the token-provider-cleanup to ocata, since
Lance performed the work for it this release.

Change-Id: I7b7ce6353db91d6203402e42b8bb887bff0ae032
This commit is contained in:
Steve Martinelli 2016-12-21 21:46:26 -05:00
parent 30ffca62e9
commit 1704c80c57
2 changed files with 29 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

0
superseded/token-provider-cleanup.rst → specs/keystone/ocata/token-provider-cleanup.rst
View File

29
superseded/README.rst Normal file
View File

@ -0,0 +1,29 @@
The 'superseded' directory contains a list of specifications that were approved,
but then superseded by another specification.
The various folders named after release cycles in ``specs/keystone/`` should
reflect the final state of features that were implemented in that cycle.
When the release cycle has ended, move any spec that was superseded to this
folder, and add any reasoning to this file.
* spec: functional-testing-setup.rst
* reason: decided to use ``keystone/ongoing/functional-testing.rst`` instead.
* spec: online-schema-migration.rst
* reason: decided to use ``keystone/newton/manage-migration.rst`` instead
* spec: ldap3.rst
* reason: used the py3 fork of python-ldap (pyldap) instead, see:
https://blueprints.launchpad.net/keystone/+spec/python3 for details.
* spec: password-totp-plugin.rst
* reason: decided to use ``keystone/ocata/per-user-auth-plugin-requirements.rst`` instead
* spec: unscoped-catalog.rst
* reason: core team decided it was no longer valid, spec was abandoned.