Erlang
lang
Erlang is a general-purpose, concurrent, functional high-level programming language, and a garbage-collected runtime system. The term Erlang is used interchangeably with Erlang/OTP, or Open Telecom Platform (OTP), which consists of the Erlang runtime system, several ready-to-use components (OTP) mainly written in Erlang, and a set of design principles for Erlang programs.
| Release | Released | Active Support | Security Support | Latest |
|---|---|---|---|---|
| 26 | 11 months ago (15 May 2023) |
Yes |
Ends
in 2 years (15 May 2026)
|
26.2.4
(12 Apr 2024)
|
| 25 | 1 year and 11 months ago (17 May 2022) |
Ended
11 months ago (15 May 2023)
|
Ends
in 1 year (17 May 2025)
|
25.3.2.11
(12 Apr 2024)
|
| 24 | 2 years and 11 months ago (10 May 2021) |
Ended
1 year and 11 months ago (17 May 2022)
|
Ends
in 1 week and 6 days (10 May 2024)
|
24.3.4.17
(08 Apr 2024)
|
| 23 | 3 years and 11 months ago (11 May 2020) |
Ended
2 years and 11 months ago (10 May 2021)
|
Ended
10 months ago (05 Jun 2023)
|
23.3.4.20
(14 Mar 2024)
|
| 22 | 4 years and 11 months ago (10 May 2019) |
Ended
3 years and 11 months ago (11 May 2020)
|
Ended
1 year and 11 months ago (10 May 2022)
|
22.3.4.27
(18 Mar 2024)
|
| 21 | 5 years and 10 months ago (19 Jun 2018) |
Ended
4 years and 11 months ago (10 May 2019)
|
Ended
2 years and 10 months ago (19 Jun 2021)
|
21.3.8.24
(31 May 2021)
|
| 20 | 6 years and 10 months ago (21 Jun 2017) |
Ended
5 years and 10 months ago (19 Jun 2018)
|
Ended
3 years and 10 months ago (21 Jun 2020)
|
20.3.8.26
(27 Feb 2020)
|
| 19 | 7 years and 10 months ago (21 Jun 2016) |
Ended
6 years and 10 months ago (21 Jun 2017)
|
Ended
4 years and 10 months ago (21 Jun 2019)
|
19.3.6.13
(08 Jan 2019)
|
| 18 | 8 years ago (23 Jun 2015) |
Ended
7 years and 10 months ago (21 Jun 2016)
|
Ended
5 years ago (09 Nov 2018)
|
18.3.4.11
(09 Nov 2018)
|
| 17 | 10 years ago (07 Apr 2014) |
Ended
8 years ago (23 Jun 2015)
|
Ended
5 years ago (11 Oct 2018)
|
17.5.6.10
(11 Oct 2018)
|
Erlang/OTP does not follow Semantic Versioning. However, it does follow some
of its principles with a two to four parts version number, <Major>.<Minor>.<Patch>.<X>, where:
-
<Major>increments when there are major or incompatible changes, -
<Minor>increments when there are new features, -
<Patch>(optional) increments when there are pure bug fixes, -
<X>(optional) is a part used for partially ordered versions.
More information about the versioning scheme can be found in the Erlang/OTP documentation.
The release policy is not documented, but looking at the latest releases it seems that a new major version is released every year in May and supported for approximately 3 years.
According to Erlang/OTP’s support policy, bugs are in general only fixed on the latest release, and new features are introduced in the upcoming release. In practice, small improvements are regularly added to the latest release, and major bug and security fixes are backported to the supported previous releases.
More information is available on the Erlang website.
You should be running one of the supported release numbers listed above in the rightmost column.
You can submit an improvement to this page
on GitHub
.
This page has a corresponding
Talk Page.
A JSON version of this page is available at /api/erlang.json. See the API Documentation for more information. You can subscribe to the iCalendar feed at /calendar/erlang.ics.