Owners

Current status

Detailed Description

Erlang is a general-purpose concurrent programming language and runtime system. The sequential subset of Erlang is a functional language, with strict evaluation, single assignment, and dynamic typing. For concurrency it follows the Actor model. It was designed by Ericsson to support distributed, fault-tolerant, soft-real-time, non-stop applications. The first version was developed by Joe Armstrong in 1986. It supports hot swapping, thus code can be changed without stopping a system. Erlang was originally a proprietary language within Ericsson, but was released as open source in 1998.

While threads are considered a complicated and error-prone topic in most languages, Erlang provides language-level features for creating and managing processes with the aim of simplifying concurrent programming. Though all concurrency is explicit in Erlang, processes communicate using message passing instead of shared variables, which removes the need for locks.

The status of Erlang and related packages in Fedora/EPEL is shown at Erlang SIG page.

Benefit to Fedora

Several notable improvements were introduced in this version. Some highlights are:

Line number and filename information are now included in exception backtraces. This information will be pretty-printed in the shell and used in crash reports etc. In practice it will be much easier to find where something failed.

The driver interface has been changed to enable 64-bit aware drivers. Most importantly the return types for ErlDrvEntry callbacks 'call' and 'control' has been changed which require drivers to be changed.

CommonTest hooks are now in a final supported version.

There is a new GUI tool in the observer application which integrates pman, etop, appmon and tv into one tool. The tool does also contain functions for activating tracing in an easy way.

The Erlang distribution can now be run over the new SSL implementation.

Scope

Rebuild all dependent packages. At this step we must carefully check for possible usage of obsoleted functions, for added/removed runtime requirements and provide/send upstream patches when necessary. ETA: 28-02-2011. I expect some issues at least due to incompatible changes in erl_driver API.

How To Test

Collect feedback from volunteers regarding their experience with this Erlang/OTP version

Contingency Plan

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.