I'm not suggesting we increase Oslo responsibilities, but that we need a non fire drill way to signal that the work hasn't been done. On 10 Dec 2015 6:42 PM, "Davanum Srinivas" <davanum at gmail.com> wrote: > Rob, > > This is a shared responsibility. I am stating that projects using oslo > are failing to take up their share of things to be done. No, we should > not increase more responsibility on Oslo team. > > -- Dims > > On Thu, Dec 10, 2015 at 8:25 AM, Robert Collins > <robertc at robertcollins.net> wrote: > > On 10 December 2015 at 18:19, Davanum Srinivas <davanum at gmail.com> > wrote: > >> So clearly the deprecation process is not working as no one looks at > >> the log messages and fix their own projects. Sigh! > > > > I think we need some way to ensure that a deprecation has been done: > > perhaps a job that we can run on each oslo project which fails if > > deprecated things are in use; we can have that on non-voting, and then > > use it to detect the release in which we can start the removal clock > > for a deprecated thing. > > > > -Rob > > > > > __________________________________________________________________________ > > OpenStack Development Mailing List (not for usage questions) > > Unsubscribe: > OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > -- > Davanum Srinivas :: https://twitter.com/dims > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151210/f4ec89fb/attachment.html>