We are planning to release a stable version often, around once a month or a little more often.
See Branches for a description of the branches in the erlide repository.
Whenever a fix is done or a feature is implemented, it is merged in
pu. At the time for a release, the following actions happen:
masterbranch is moved to the current
nextthat have been tested as stable and complete are merged into
nexton top of
puthat are deemed stable and complete are merged into
puis rebased on top of
lateris rebased on top of
Then a stable release is built from
master and an unstable release from
Did you find errors in the documentation? Do you have improvements to suggest? Suggest edits!