aboutsummaryrefslogtreecommitdiff
path: root/website/content/en/status/report-2024-10-2024-12/erlang.adoc
diff options
context:
space:
mode:
Diffstat (limited to 'website/content/en/status/report-2024-10-2024-12/erlang.adoc')
-rw-r--r--website/content/en/status/report-2024-10-2024-12/erlang.adoc24
1 files changed, 24 insertions, 0 deletions
diff --git a/website/content/en/status/report-2024-10-2024-12/erlang.adoc b/website/content/en/status/report-2024-10-2024-12/erlang.adoc
new file mode 100644
index 0000000000..017e18c87c
--- /dev/null
+++ b/website/content/en/status/report-2024-10-2024-12/erlang.adoc
@@ -0,0 +1,24 @@
+=== FreeBSD Erlang Ecosystem Ports update
+
+Links: +
+link:https://wiki.freebsd.org/Erlang[FreeBSD Erlang wiki] URL: link:https://wiki.freebsd.org/Erlang[] +
+link:https://erlang.org/[Erlang/OTP language] URL: link:https://erlang.org/[] +
+link:https://elixir-lang.org/[Elixir language] URL: link:https://elixir-lang.org/[] +
+link:https://gleam.run/[Gleam language] URL: link:https://gleam.run/[] +
+
+Contact: FreeBSD Erlang mailing list <erlang@FreeBSD.org>
+
+The Erlang runtime system, commonly known as the BEAM, provides a runtime that is used by a number of programming languages and applications in the FreeBSD ports collection.
+
+In the final update for 2024, the Erlang ecosystem team has been busy:
+
+* Regular updates to all Erlang/OTP releases, to stay current
+* Elixir 1.18.1, Gleam 1.6.3, and RabbitMQ updates
+
+Users of RabbitMQ need to update each quarter to avoid being stuck on an unsupported release of Erlang/OTP + RabbitMQ, without a supported migration path.
+
+Note that as the upstream Erlang OTP team only commit to supporting the two latest major releases, more and more point updates are arriving for OTP26-27, but not for the older Erlang runtime releases, which are now unlikely to get security and bug fixes.
+
+The Erlang team will be updating the default Erlang runtime to OTP26, to package:lang/erlang[], along with the usual dependencies and tooling.
+
+Additional testing and community contributions are welcome; please reach out on the mailing list, especially if you are able to help testing of specific port updates.