TL;DR: if you provision Erlang packages from Team RabbitMQ's Bintray org, please switch to
from Bintray, no action is required.
Dear RabbitMQ users,
Some of you provision recent Erlang releases from the RabbitMQ org on Bintray .
Around November 2018 our team switched our pipeline that produces Erlang builds
to use a separate org . There were no new builds published to  and  since then.
The reason for this move is Bintray's notorious policy of blocking downloads for projects
on the open source plan when certain quotas are exceeded. We'd like to minimise the risk
of this happening again so large Erlang packages were moved to a separate org.
If it gets blocked, at least RabbitMQ downloads on Bintray would not be affected.
doc guides  were updated shortly after but a lot of early adopters
keep using  and , even though they don't get new Erlang versions that way and
we've marked the packages as deprecated. According to our estimates, Erlang installations
from the main org account for a good third of the bandwidth quota. This is a significant
volume of traffic we would really like to migrate away from the main org.
As such, we will be PERMANENTLY REMOVING Erlang packages from the main Bintray org  on April 29th, 2019. If you provision Erlang from  or , please switch to the new org .
The new repo provides the latest Erlang patch releases. There are no reasons to stick to the
Switching over is a matter of updating one or two lines in apt and yum repository definitions.
Documentation guides on rabbitmq.com
 use new repositories,
so please take a look at what they recommend.
Repository signing keys are identical for both orgs. There is no need to reimport the key.
In case you have any questions about this migration, ask away in this thread.