About the open-source and commercial releases
Thu Dec 9 11:05:48 CET 2004
Ingela Anderton <ingela@REDACTED> writes:
> I actually was a little surprised that the patch had not made it
> to the open source version yet, the patch must just have missed the
> last open source release.
It is not directly related to the original question, but I will
take this opportunity to inform about open-source and commercial
releases, and how we now try to break the "old tradition" of releasing
the R*B-1 release more than six months after the original R*B release.
We never intended to delay the initial bug fix release by six months.
It was just that there was another necessary correction to some appliation
or the other that could be included if we just waited a few days more. When
that correction was finished, we could have another great correction in
another application if we just waited four days more... and so on.
Therefore, our current policy is to release the open-source releases regularily,
at least once every two months. Generally, we set our internal deadline
for when the next release will be out, and patches that are not ready will
have to wait for the next release.
We've have always had the policy that paying customers should have access
to patches before we release them as open-source.
We usually don't announce beforehand when an open-source release is to be released,
but this time I can tell that it is very likely that R10B-2 will be released
Björn Gustavsson, Erlang/OTP, Ericsson AB
More information about the erlang-questions