Comment 3 for bug 1715141

Let's push the removal off to the T release. No point in breaking things if we can avoid it. Besides there are still a few other users of blocking out there who will also be affected.

Per Ben's suggestion if projects still require blocking at T+, we can support its use by having the projects add an

oslo.messaging.executors =
   blocking = futurist:SynchronousExecutor

to their setup.cfg to keep it available to them even if we drop it from oslo.messaging itself.

See the email thread:

http://lists.openstack.org/pipermail/openstack-dev/2018-October/135825.html