####This is not a supported branch, it is informational ONLY!
Basho OTP should be built from one of the following branches or tags. If you're building for any use approximating production, we strongly encourage you to use a tagged production release.
|Status||Base||Branch||Release Tag||Stable B/T|
All Basho branches are named with the prefix basho - any other branch name is simply updated periodically, unchanged, from Ericsson's repository.
For any given Basho OTP NN version, the current stable branch is
basho-otp-NN and work-in-progress branches are
Updates from the main Erlang repository are merged from the appropriate maintenance branch into
basho-otp-NN periodically, usually at tagged point releases.
Further information on branches can be found in README and Release Notes files on the branches themselves.
Our modifications to the original distribution generally fall into one or more of the following categories:
Our users care a lot about performance, and we do what we can to get the best out of our products running on Erlang/OTP.
In general, we tighten up security in our releases where it makes sense for us to do so.
- Stability & Scalability
Erlang/OTP is pretty stable and scalable, but when we find an area where we can improve it for running our applications, we do.
####Where it Works
Erlang/OTP is designed to run on a wide array of platforms, while our products are not. As such, we only qualify our releases on 64-bit operating systems running on x86_64 processors. Specific versions are listed for our products, but our focus is on relatively current versions of:
- OS X
Our releases should be fully interoperable with unmodified Erlang/OTP distributions, but not necessarily in their default configurations. We DO change a few default settings, but generally accept the same configuration options to set them explicitly.
No, we don't do Windows, and we don't even do all available versions of the systems listed above. While we do try to keep our changes as portable as the original distributions they're based on, we don't test beyond what our products support.
###Building and Installing
General information on building and installing Erlang/OTP can be found in the $ERL_TOP/HOWTO/INSTALL.md document.
Specific instructions for building Basho's OTP releases can be found in the README file on the branch you're building.
Our version identifiers correlate to the Erlang/OTP release without the basho suffix, but our changes to individual ERTS components and OTP applications may not always carry distinct versions due to release process issues with older versions. Our releases are intended to be used as a single cohesive installation, we do NOT support mixing components between our releases and the original distributions.
###Contributing to Erlang/OTP
Unless you want to suggest a patch to our specific Erlang/OTP changes, if you find something you think needs to be changed you'll want to refer to the Erlang instructions for submitting bug reports or patches.
If your patch pertains specifically to our version, forking and creating a pull request on GitHub is the best way to get us to consider it. Bear in mind, however, that our releases are tailored to our needs, so if it's not directly pertinent to how our users deploy Erlang/OTP, it may not be of interest to us.
###Copyright and License
Everything in Erlang/OTP, whether part of the original distribution or a contribution of ours, is subject to the terms of the license applied to it in Ericsson's repository. Through OTP-17, that was the Erlang Public License. Beginning with OTP-18, the Apache License, Version 2.0 applies.