releases/deliverables/stein/keystone.yaml
Előd Illés 9b2a256f93 [keystone] Transition Stein to EM
This transition the stein branch to extended maintenance.
Changes for bugfixes and things the team deems important are
still encouraged, but there will no longer be official releases
off of the branch.

Please +1 if the team is ready for us to proceed with this
transition, or -1 if there are any final backports currently in
flight that we should wait for. For the latter case, please
update the patch with the new commit hash after doing a final
release to get those changes out so we know to proceed with the
transition.

Change-Id: I4f9c1987dbe7a999d851d798269482ed44c21731
2020-11-11 23:17:34 +01:00

51 lines
1.9 KiB
YAML

---
launchpad: keystone
release-model: cycle-with-rc
team: keystone
type: service
repository-settings:
openstack/keystone: {}
releases:
- projects:
- hash: 1f1522703cfa25a533b7462aa402ac30128473e3
repo: openstack/keystone
version: 15.0.0.0rc1
- projects:
- hash: c78581b4608f3dc10e945d358963000f284f188a
repo: openstack/keystone
version: 15.0.0.0rc2
- diff-start: 14.0.0.0rc1
projects:
- hash: c78581b4608f3dc10e945d358963000f284f188a
repo: openstack/keystone
version: 15.0.0
- version: 15.0.1
projects:
- repo: openstack/keystone
hash: 95b2bbeab113d9f04d1c81f7f1b48bf692bce979
- version: stein-em
projects:
- repo: openstack/keystone
hash: 95b2bbeab113d9f04d1c81f7f1b48bf692bce979
branches:
- location: 15.0.0.0rc1
name: stable/stein
cycle-highlights:
- This release introduced Multi-Factor Authentication Receipts, which
facilitates a much more natural sequential authentication flow when
using MFA.
- The limits API now supports domains in addition to projects, so
quota for resources can be allocated to top-level domains and distributed
among children projects.
- JSON Web Tokens are added as a new token format alongside fernet
tokens, enabling support for a internet-standard format. JSON Web
Tokens are asymmetrically signed and so synchronizing private keys
across keystone servers is no longer required with this token format.
- Multiple keystone APIs now support system scope as a policy target,
which reduces the need for customized policies to prevent global
access to users with an admin role on any project.
- Multiple keystone APIs now use default reader, member, and admin
roles instead of a catch-all role, which reduces the need for customized
policies to create read-only access for certain users.
release-notes: https://docs.openstack.org/releasenotes/keystone/stein.html