On Thu, May 12, 2016 at 6:39 PM, gordon chung <g...@live.ca> wrote: > > can anyone confirm when we deprecated keystonev2? i see a bp[1] related > to deprecation that was 'implemented' in 2013. > > We did this last release, see the sixth bullet point here:
http://docs.openstack.org/releasenotes/keystone/mitaka.html#deprecation-notes I also vocalized this on the regular, -dev, and -ops mailing list. > i realise switching to v3 breaks many gates but it'd be good to at some > point say it's not 'keystonev3 breaking the gate' but rather 'projectx > is breaking the gate because they are using keystonev2 which was > deprecated 4 cycles ago'. given the deprecation period allowed already, > can we say "here's some help, fix/merge this by > <date_before_end_of_newton>, or your gate will be broken until then"? > (assuming all the above items by Raildo doesn't fix everything). > > [1] https://blueprints.launchpad.net/keystone/+spec/deprecate-v2-api > > cheers, > > -- > gord > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
