F43 Change Proposal: Erlang 27 (self-contained)

Erlang 27

This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.

Wiki
Announced

:link: Summary

Update Erlang/OTP to version 27.

:link: Owner

:link: Current status

  • Targeted release: Fedora 43
  • Last updated: 2025-05-22

:link: Detailed Description

Upgrade Erlang to version 27 which brings a lot of changes. Just a few highlights from many:

  • Triple-Quoted strings
  • Sigils
  • The new json module
  • Process labels
  • New functionality in STDLIB
  • New SSL client-side stapling support
  • Lots of bugfixes

Aside from this, we plan to further improve quality of Erlang and related packages. These are shortcomings we want to address:

  • Finish switching to rebar3 as a main build tool and deprecate rebar2.
  • Improve Erlang Packaging Guidelines and promote it as the official guideline.
  • SELinux rules for main Erlang applications (Ejabberd, CouchDB, RabbitMQ) are still outdated or missing.

:link: Benefit to Fedora

Fedora users, both developers and end-users, will have visible benefits from using Fedora-provided packages. Namely:

  • Improved scalability and robustness.
  • Much easier developing and debugging.

:link: Scope

  • Proposal owners:
    • Upgrade Erlang to the 27 version.
    • Upgrade outdated packages:
      • Ejabberd
      • RabbitMQ.
    • Package GDB macros for easier coredump debugging (see also this ticket).
  • Other developers: N/A
  • Release engineering: TBA
  • Policies and guidelines:
  • Trademark approval: N/A (not needed for this Change)

:link: Upgrade/compatibility impact

  • N/a

:link: How To Test

  • Ensure that high-grade Erlang applications are still working:
Name Tested
ejabberd No
elixir No
rabbitmq-server No
  • Collect feedback from volunteers regarding their experience with this Erlang/OTP version

:link: User Experience

Users will get more robust, scalable, and fast Erlang applications.

:link: Dependencies

The following packages must be rebuilt: NIF-libraries.

:link: Contingency Plan

  • Contingency mechanism: None necessary. Instead of falling back to the previous version we should fix existing packages in order to help the Community. We should also monitor upstream development process for potentially discovered issues and proactively apply patches (as we already did with Erlang R14, Erlang R15, Erlang R16, Erlang 17, Erlang 18, Erlang 19, Erlang 20, Erlang 21, Erlang 22, Erlang 23, Erlang 24, and Erlang 25). It should be noted that this change consists from an independent or loosely coupled smaller changes. If we fail to deliver some changes in time, we should reschedule these exact changes to the future Fedora release while keeping already implemented ones.
  • Contingency deadline: N/A
  • Blocks release? N/A
  • Blocks product? N/A

:link: Documentation

:link: Release Notes

Erlang/OTP 25.0 is available in Fedora 43.

Last edited by @amoloney 2025-06-02T20:30:10Z

Last edited by @amoloney 2025-06-02T20:30:10Z

How do you feel about the proposal as written?

  • Strongly in favor
  • In favor, with reservations
  • Neutral
  • Opposed, but could be convinced
  • Strongly opposed
0 voters

If you are in favor but have reservations, or are opposed but something could change your mind, please explain in a reply.

We want everyone to be heard, but many posts repeating the same thing actually makes that harder. If you have something new to say, please say it. If, instead, you find someone has already covered what youโ€™d like to express, please simply give that post a :heart: instead of reiterating. You can even do this by email, by replying with the heart emoji or just โ€œ+1โ€. This will make long topics easier to follow.

Please note that this is an advisory โ€œstraw pollโ€ meant to gauge sentiment. It isnโ€™t a vote or a scientific survey. See About the Change Proposals category for more about the Change Process and moderation policy.