Open Stack

The change I made to build tokens from existing data (rather than
re-querying it all from the db) didn't go in?

Without it extensions are not able to build custom tokens (meaning just
about any extension that wants to do something with auth is not possible).


On Thu, Mar 28, 2013 at 2:34 AM, Thierry Carrez <thierry at openstack.org>wrote:

> Hello everyone,
>
> Due to the renaming of the trust extension and a response backward
> compatibility issue, we created a new Grizzly release candidate for
> OpenStack identity ("Keystone").
>
> You can find the RC2 tarball and the list of fixed bugs at:
> https://launchpad.net/keystone/grizzly/grizzly-rc2
>
> This is hopefully the last Grizzly release candidate for Keystone.
> Unless new release-critical regressions are found that warrant another
> release candidate respin, this RC2 will be formally included in the
> common OpenStack 2013.1 final release next week. You are therefore
> strongly encouraged to test and validate this tarball.
>
> Alternatively, you can grab the code at:
> https://github.com/openstack/keystone/tree/milestone-proposed
>
> If you find a regression that could be considered release-critical,
> please file it at https://bugs.launchpad.net/keystone/+filebug and tag
> it *grizzly-rc-potential* to bring it to the release crew's attention.
>
> Happy regression hunting,
>
> --
> Thierry Carrez (ttx)
> Release Manager, OpenStack
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20130328/d680884d/attachment.html>