On Mon, Mar 24, 2008 at 07:00:08PM +0800, Raymond Xiong wrote: > I don't have specific reason, but I observed other language(ie., > Ruby, Java, Perl, etc.) were all packaged in this way. I think > it's good to have this flexibility?
There is such a thing as "too much rope". There are significant incompatibilities between versions of Java, and reasonable ones between the two versions of Perl. I can't speak for Ruby. There are minor ones between 2.3 and 2.4 of Python. If released versions of Erlang are expected to be incompatible, and flag-days aren't suitable for the customer base, then two versions may be kept on the system. > Because Erlang/OTP R12B release is rather new, it is probably > not well tested and supported for some applications. For example, > below is from ejabberd README on which Erlang version to use: > > "Erlang/OTP R10B-9 up to R11B-5. Erlang R12 releases are not yet > officially supported, and are not recommended for production > servers" Erm, perhaps this means that we shouldn't be delivering it, and using R11 for a while? Danek
