Hello community, here is the log from the commit of package rubygem-bunny for openSUSE:Factory checked in at 2015-08-05 06:50:30 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/rubygem-bunny (Old) and /work/SRC/openSUSE:Factory/.rubygem-bunny.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "rubygem-bunny" Changes: -------- --- /work/SRC/openSUSE:Factory/rubygem-bunny/rubygem-bunny.changes 2015-02-11 16:45:13.000000000 +0100 +++ /work/SRC/openSUSE:Factory/.rubygem-bunny.new/rubygem-bunny.changes 2015-08-05 06:50:33.000000000 +0200 @@ -1,0 +2,72 @@ +Fri Jul 24 04:28:51 UTC 2015 - [email protected] + +- updated to version 2.0.0 + see installed ChangeLog.md + + ## Changes between Bunny 1.7.0 and 2.0.0 + + Bunny `2.0` doesn't have any breaking API changes + but drops Ruby 1.8 and 1.9 (both EOL'ed) support, + hence the version. + + ### Minimum Required Ruby Version is 2.0 + + Bunny `2.0` requires Ruby 2.0 or later. + + ## Non-Blocking Writes + + Bunny now uses non-blocking socket writes, uses a reduced + number of writes for message publishing (frames are batched + into a single write), and handles TCP back pressure from + RabbitMQ better. + + Contributed by Irina Bednova and Michael Klishin. + + ### Reduced Timeout Use + + `Bunny::ContinuationQueue#poll` no longer relies on Ruby's `Timeout` which has + numerous issues, including starting a new "interruptor" thread per operation, + which is far from efficient. + + Contributed by Joe Eli McIlvain and Carl Hörberg. + + ### Capped Number of Connection Recovery Attempts + + `:recovery_attempts` is a new option that limits the number of + connection recovery attempts performed by Bunny. `nil` means + "no limit". + + Contributed by Irina Bednova. + + ### Bunny::Channel#basic_ack and Related Methods Improvements + + `Bunny::Channel#basic_ack`, `Bunny::Channel#basic_nack`, and `Bunny::Channel#basic_reject` + now adjust delivery tags between connection recoveries, as well as have a default value for + the second argument. + + Contributed by Wayne Conrad. + + ### Logger Output Remains Consistent + + Setting the `@logger.progname` attribute changes the output of the logger. + This is not expected behaviour when the client provides a custom logger. + Behaviour remains unchainged when the internally initialized logger is used. + + Contributed by Justin Carter. + + ### prefetch_count is Limited to 65535 + + Since `basic.qos`'s `prefetch_count` field is of type `short` in the protocol, + Bunny must enforce its maximum allowed value to `2^16 - 1` to avoid + confusing issues due to overflow. + + ### Per-Consumer and Per-Channel Prefetch + + Recent RabbitMQ versions support `basic.qos` `global` flag, controlling whether + `prefetch` applies per-consumer or per-channel. Bunny `Channel#prefetch` now + allows flag to be set as optional parameter, with the same default behaviour as + before (per-consumer). + + Contributed by tiredpixel. + +------------------------------------------------------------------- Old: ---- bunny-1.7.0.gem New: ---- bunny-2.0.0.gem ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ rubygem-bunny.spec ++++++ --- /var/tmp/diff_new_pack.46gUqn/_old 2015-08-05 06:50:34.000000000 +0200 +++ /var/tmp/diff_new_pack.46gUqn/_new 2015-08-05 06:50:34.000000000 +0200 @@ -24,7 +24,7 @@ # Name: rubygem-bunny -Version: 1.7.0 +Version: 2.0.0 Release: 0 %define mod_name bunny %define mod_full_name %{mod_name}-%{version} ++++++ bunny-1.7.0.gem -> bunny-2.0.0.gem ++++++ ++++ 4663 lines of diff (skipped)
