1704c80c57
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
1.0 KiB
1.0 KiB
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.
- reason: decided to use
- spec: online-schema-migration.rst
- reason: decided to use
keystone/newton/manage-migration.rst
instead
- reason: decided to use
- 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
- reason: decided to use
- spec: unscoped-catalog.rst
- reason: core team decided it was no longer valid, spec was abandoned.