Skip to content
Erlang C C++ Makefile Java HTML Other
Latest commit 523e048 Mar 17, 2016 @proxyles proxyles Merge tag 'OTP-' into maint-18
=== OTP- ===

Changed Applications:
- diameter-
- erts-
- ssl-

Unchanged Applications:
- asn1-3.0.4
- common_test-1.10.1
- compiler-5.0.4
- cosEvent-2.1.15
- cosEventDomain-1.1.14
- cosFileTransfer-1.1.16
- cosNotification-1.1.21
- cosProperty-1.1.17
- cosTime-1.1.14
- cosTransactions-1.2.14
- crypto-3.5
- debugger-
- dialyzer-2.7.4
- edoc-0.7.16
- eldap-1.1.1
- erl_docgen-0.3.7
- erl_interface-3.7.20
- et-1.5
- eunit-2.2.9
- gs-1.5.16
- hipe-3.11.3
- ic-4.3.6
- inets-5.10.9
- jinterface-1.5.12
- kernel-
- megaco-3.17.3
- mnesia-4.12.5
- observer-2.0.4
- odbc-2.10.22
- orber-3.7.1
- os_mon-2.3.1
- ose-1.0.2
- otp_mibs-1.0.10
- parsetools-2.0.12
- percept-0.8.10
- public_key-0.23
- reltool-0.6.6
- runtime_tools-
- sasl-2.4.1
- snmp-5.1.2
- ssh-3.2.4
- stdlib-2.4
- syntax_tools-1.6.18
- test_server-3.8.1
- tools-2.7.2
- typer-0.9.8
- webtool-0.8.10
- wx-1.3.3
- xmerl-1.3.7



Erlang is a programming language used to build massively scalable soft real-time systems with requirements on high availability. Some of its uses are in telecom, banking, e-commerce, computer telephony and instant messaging. Erlang's runtime system has built-in support for concurrency, distribution and fault tolerance.

OTP is set of Erlang libraries and design principles providing middle-ware to develop these systems. It includes its own distributed database, applications to interface towards other languages, debugging and release handling tools.


BEAM is the name of the virtual machine where all Erlang code is executed. Every compiled Erlang file has the suffix .beam. The virtual machine is sometimes referred to as the emulator.

ERTS is the Erlang Runtime System where the BEAM, kernel and standard libraries amongst others are included.

More information can be found at

Building and Installing

Information on building and installing Erlang/OTP can be found in the $ERL_TOP/HOWTO/ document.

Contributing to Erlang/OTP

Here are the instructions for submitting patches.

In short:

  • We prefer to receive proposed updates via email on the erlang-patches mailing list or through a pull request.

  • Pull requests will be handled once everyday and there will be essential testing before we will take a decision on the outcome of the request. If the essential testings fails, the pull request will be closed and you will have to fix the problem and submit another pull request when this is done.

  • We merge all proposed updates to the pu (proposed updates) branch, typically within one working day.

  • At least once a day, the contents of the pu branch will be built on several platforms (Linux, Solaris, Mac OS X, Windows, and so on) and automatic test suites will be run. We will email you if any problems are found.

  • If a proposed change builds and passes the tests, it will be reviewed by one or more members of the Erlang/OTP team at Ericsson. The reviewer may suggest improvements that are needed before the change can be accepted and merged.

  • Once or twice a week, a status email called "What's cooking in Erlang/OTP" will be sent to the erlang-patches mailing list.

Bug Reports

Please look at the instructions for submitting bugs reports.

Copyright and License


Copyright Ericsson AB 2010-2014. All Rights Reserved.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.


Something went wrong with that request. Please try again.