Skip to content

Heads up: Erlang 24 is released #483

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
michaelklishin opened this issue May 12, 2021 · 2 comments · Fixed by #486
Closed

Heads up: Erlang 24 is released #483

michaelklishin opened this issue May 12, 2021 · 2 comments · Fixed by #486

Comments

@michaelklishin
Copy link
Collaborator

michaelklishin commented May 12, 2021

This is not an issue but a heads-up: Erlang 24 has shipped earlier today. RabbitMQ 3.8.16 supports it already.

Our tests revealed no issues beyond fairly obscure Erlang tooling incompatibility with Erlang 24 (e.g. Looking Glass). Those
obviously will take some time to be addressed across the ecosystem.

Erlang 24 provides substantial (usually double digit %) throughput gains for many RabbitMQ workloads, so we expect
its adoption in this image will become a commonly requested thing.

I don't know if this image's build system automatically bumps major Erlang versions (@gerhard) but it likely does not.
Therefore we need to decide when to make the switch. Some members of the core team suggested late June when
24.0 becomes 24.0.2 or something similar.

@tianon
Copy link
Member

tianon commented May 19, 2021

It does auto-bump, but it's tied to a fixed major:

rabbitmq/versions.sh

Lines 4 to 7 in e62f193

# https://www.rabbitmq.com/which-erlang.html ("Maximum supported Erlang/OTP")
declare -A otpMajors=(
[3.8]='23'
)

Happy to bump that whenever y'all deem it appropriate/sane to do so. 😄

@michaelklishin
Copy link
Collaborator Author

@tianon we don't see a lot of things reported for Erlang 24.0.1, so I think we can bump

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants