FFE for oslo.messaging 1.3.0~a9

Bug #1298970 reported by Chuck Short
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
oslo.messaging (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

1.3.0a9
-------

* Remove use of sslutils

1.3.0a8
-------

* Add missing data into the notif. endpoint callback
* notification listener: add allow_requeue param
* Do not leak _unique_id out of amqp drivers
* Add multiple exchange per listerner in fake driver
* Allow to requeue the notification message
* Slow down Kombu reconnect attempts
* Don't run python 3 tests by default
* Gracefully handle consumer cancel notifications
* Updated from global requirements
* Convert to oslo.test
* Add log_handler to oslo.messaging
* Add a link to the docs from the README
* Pass the session to QpidMessage constructor
* User a more accurate max_delay for reconnects
* Make the dispatcher responsible of the message ack
* Don't reply to notification message
* Abstract the acknowledge layer of a message
* Implements notification listener and dispatcher
* Switch over to oslosphinx
* Improve help strings
* Update ExpectedException handling
* Ignore any egg and egg-info directories
* Qpid: advance thru the list of brokers on reconnect
* RabbitMQ: advance thru the list of brokers on reconnect

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package oslo.messaging - 1.3.0~a9-0ubuntu1

---------------
oslo.messaging (1.3.0~a9-0ubuntu1) trusty; urgency=medium

  * New upstream release (LP: #1298970)
  * debian/control:
    - Add python-oslotest as a build dependency.
    - Use python-oslosphinx instead of python-oslo.sphinx
 -- Chuck Short <email address hidden> Thu, 27 Mar 2014 13:01:34 -0400

Changed in oslo.messaging (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.