keystone-specs/superseded
Steve Martinelli 1704c80c57 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
2017-01-06 21:37:51 +00:00
..
README.rst add a README file to the superseded spec folder 2017-01-06 21:37:51 +00:00
functional-testing-setup.rst clean up spec repo 2016-02-03 01:52:27 -05:00
ldap3.rst clean up the spec repo for newton 2016-09-06 10:38:07 -07:00
online-schema-migration.rst clean up the spec repo for newton 2016-09-06 10:38:07 -07:00
password-totp-plugin.rst clean up approved specs for ocata 2016-12-08 22:28:20 -05:00
unscoped-catalog.rst clean up spec repo 2016-02-03 01:52:27 -05:00

README.rst

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
  • 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.