Danek Duvall wrote: > On Mon, Mar 24, 2008 at 02:42:02PM -0600, Jim Walker wrote: > >>>> 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" >> I think this is more of a timing thing. The ejabberd 2.0.0 release >> was made 2/20/08 and the first Erlang R12 release was made 12/5/07, >> and the second was made on 2/6/08. Depending on how they qualify >> ejabberd releases, Erlang R12 probably wasn't an option in terms >> of inclusion into their final test cycle. Erlang R11B-5 was released >> 1/13/07. >> >> The ejabberd development version is now at 2.3.0, and is moving >> faster than erlang. I don't see any major issues in the bugs or >> logs with R12. >> >> Raymond has the best experience to decide what versions of Erlang >> and Ejabberd to use. > > Are we sticking with the originally proposed versions? I think this is the > only open question at the moment.
Yes. Raymond determined that Erlang/OTP R12B1 was the best version to use, which was in the initial proposal. Cheers, Jim
