Use proper airbrake notification method
Provide metadata with messages
Make dev look like prod

There is no need to have a prod environment in this example project.
Make dev behave like prod for the benefit of benchmark tests.
Add additional configuration options

Ability to specify bunny's network recovery interval; and whether to
auto delete the queue and exchange (helpful for cleaning up after
running tests).
Bump version

New minor version to indicate significant changes to internal behaviour
of rabbit_feed
Make logging more consistent with other example project
Remove connection recovery

Connection recovery in bunny has improved since the creation of
rabbit_feed. The purpose of this change is to simplify rabbit_feed by
letting bunny manage its own connection recovery.
Connection recovery testing script

A script that can be used to assist with testing rabbit_feed's ability
to recover from dropping connections.
Compile assets in dev

This was an oversight when I copied the prod config over - This enables
dev to find the JS and CSS resources
More robust publishing and consuming

Using the recovery test script, I was able to simulate poor network
conditions, which highlighted some areas where the bunny default
recovery wasn't so good. This will ensure that publishing will retry
and reset the connection in the correct cases. This will ensure that
the consumer auto-recovers in case connection is lost.
Specs for consumer connection

Improve unit test coverage
Specs for producer connection

Improve unit test coverage
Specs for connection

Improve unit test coverage
Remove unused variable
Added missing specs
Updating benchmark results with latest changes
Change name back to connection pool, as this is better reflects the class naming
Refactoring as suggested by @calo81
Adjust date
Merge branch 'master' into manage_connections_better