Routing key is stripped about rabbitmq-recent-history-exchange HOT 5 CLOSED

Actually, the routing_key is there for new messages delivered while the queue is bound, but all old messages that are put into the queue on bind don't have a routing_key.

from rabbitmq-recent-history-exchange.

Maybe bump the version number (1.2.1?) and release a new version to https://www.rabbitmq.com/community-plugins.html ? I can do it, is it just to post the .ez file to the mailing list?

from rabbitmq-recent-history-exchange.

No, it doesn't work like that, we have a build system for community plugins. I'll ask @dumbbell

from rabbitmq-recent-history-exchange.

A new version of the plugin should we up on our community plugins page
On Fri, May 22, 2015 at 9:33 AM Carl Hörberg [email protected]
wrote:

Maybe bump the version number (1.2.1?) and release a new version to
https://www.rabbitmq.com/community-plugins.html ? I can do it, is it just
to post the .ez file to the mailing list?

—
Reply to this email directly or view it on GitHub
#13 (comment)
.

from rabbitmq-recent-history-exchange.

@carlhoerberg, to answer your question, to publish new or updated plugins to the community page, we run the build-community-plugins.py script in rabbitmq-public-umbrella/release-build. Once done, the script deploy-community-plugins.py uploads the artifacts to www.rabbitmq.com. Finally, one has to re-deploy the website so the community-plugins.html page is updated (the website is static).

Not very straightforward or community-oriented :-)

from rabbitmq-recent-history-exchange.