1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
|
Erlang/OTP
==========
**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.
ERTS and BEAM
-------------
**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 [erlang.org] [1].
Building and Installing
-----------------------
Information on building and installing Erlang/OTP can be found
in the [$ERL_TOP/HOWTO/INSTALL.md] [5] document.
Contributing to Erlang/OTP
--------------------------
Here are the [instructions for submitting patches] [2].
In short:
* We prefer to receive proposed updates via email on the
[`erlang-patches`] [3] 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"] [4]
will be sent to the [`erlang-patches`] [3] mailing list.
Bug Reports
--------------------------
Please look at the [instructions for submitting bugs reports] [6].
Copyright and License
---------------------
> %CopyrightBegin%
>
> 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
>
> http://www.apache.org/licenses/LICENSE-2.0
>
> 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.
>
> %CopyrightEnd%
[1]: http://www.erlang.org
[2]: http://wiki.github.com/erlang/otp/submitting-patches
[3]: http://www.erlang.org/static/doc/mailinglist.html
[4]: http://erlang.github.com/otp/
[5]: HOWTO/INSTALL.md
[6]: https://github.com/erlang/otp/wiki/Bug-reports
|
